This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

wsgi-statsd documentation

wsgi_statsd is a WSGI middleware that provides an easy way to time all requests. Integration is as easy as just wrapping your existing wsgi application.

Usage

In your wsgi.py file wrap your WSGI application as follows:

import statsd
from wsgi_statsd import StatsdTimingMiddleware


def application(environ, start_response):
    response_body = 'The request method was %s' % environ['REQUEST_METHOD']
    status = '200 OK'
    response_headers = [('Content-Type', 'text/plain'),
                        ('Content-Length', str(len(response_body)))]

    start_response(status, response_headers)

    return [response_body]

client = statsd.StatsClient(
    prefix='your_prefix',
    host='your_host',
    port=8125
)

application = StatsdTimingMiddleware(application, client)

Note

If an unhandled exception happens, it will not be timed by default. This is a design decision to separate error reporting and actual statistical measurements. To enable exception timing, pass \(time_exception=True\) to the middleware constructor:

application = StatsdTimingMiddleware(application, client, time_exceptions=True)

What it does

wsgi-statsd uses the statsd timer function, generates a key and sets the amount of time the request took as the value. The key is constructed as follows:

<statsd-client-prefix>.<separator-joined-path>.<request-method>.<response-code>.<exception-name>

Using the foo prefix, in your statsd client, and calling the www.spam.com/bar/test/ page will result in foo .bar_test.GET.200 having a value equal to the time it took to handle the request.

If you passed \(time_exceptions=True\) and any exception occurs during the response, then the key name will be postfixed with the exception class name: foo.bar_test.GET.500.ValueError.

Customizing for your needs

It’s possible to customize the way wsgi_statsd generates the key and/or time. StatsdTimingMiddleware has send_stats and get_key_name which you can override:

class CustomStatsdMiddleware(StatsdTimingMiddleware):

    def get_key_name(self, environ, response_interception):
        return super(self, CustomStatsdMiddleware).get_key_name(environ, response_interception) + '.' + environ['Transfer-Encoding']


    def send_stats(self, start, environ, response_interception):
        super(self, CustomStatsdMiddleware).send_stats(start + 10, environ, response_interception)

wsgi-statsd uses underscores as a separator for the path part of the key that is sent to statsd as that makes it easy to retrieve the data from graphite. You can override this default by passing a separator value to the middleware constructor:

StatsdTimingMiddleware(application, client, separator='.')

Contact

If you have questions, bug reports, suggestions, etc. please create an issue on the GitHub project page.

License

This software is licensed under the MIT license.

Please refer to the license file.

© 2015 Wouter Lansu, Paylogic International and others.

Changelog

0.3.1

  • Added clean target to Makefile.
  • Added the changes for the 0.2.6 version.

0.2.6

  • Updated documentation.

0.2.5

  • Fixed issue with the separator parameter. It now functions as expected and documented.

0.2.4

  • Add separator parameter to StatsdTimingMiddleware.__init__().

0.2.3

  • Add exception class name to the key when exception happens (bubenkoff)

0.2.1

  • ensure close() is properly called from the response (bubenkoff, GrahamDumpleton)
  • optionally time exceptions (bubenkoff)
  • code readability improvements (bubenkoff)

0.2.0

  • Fixed version numbers
  • Added support for WSGI applications returning generators
  • Added a test to verify that the response body remains the same after passing through the middleware

0.1.0

  • Initial public release
Release History

Release History

0.3.1

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.3.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.6

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.5

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.4

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
wsgi-statsd-0.3.1.tar.gz (6.1 kB) Copy SHA256 Checksum SHA256 Source Jan 22, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting