- Bump statsd package version to 3.3.0 (required by talisker for
configuring the statsd client)
- Add talisker.django.middleware
After this, talisker can be configured using a STATSD_DSN env var to
send out various metrics to statsd. Currently those will be timers and
counters for views; example counter:
This also results in an X-View-Name response header being added.
Example:
X-View-Name: account-index
Enabling the metrics sending part requires adding a proper STATSD_DSN
env var to talisker's execution env. Later more metrics can be added by
switching to use talisker provided `requests` session for example.
Maybe later, we can look into replacing the django_statsd based
PistonRequestTimingMiddleware metrics by these talisker provided ones.
They have a bit different naming structure (but it might be a win just
letting talisker decide here).
In most cases this is adding the MiddlewareMixin to our custom
middleware classes. Plus a version bump for django-honeypot that brings
the new style middleware compatibility.
Other middleware used (django and other 3rd party middleware) was already
compatible.
