From 7c10c7d22d49c09e4fd8733da747b288384ee361 Mon Sep 17 00:00:00 2001 From: Matt Good Date: Sun, 3 Aug 2014 13:38:07 -0700 Subject: [PATCH] Send statsd timing metrics in milliseconds The statsd documentation indicates that timing values are expected to be in milliseconds, not seconds: "The glork took 320ms to complete this time" https://github.com/etsy/statsd/blob/master/docs/metric_types.md#timing --- gunicorn/instrument/statsd.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gunicorn/instrument/statsd.py b/gunicorn/instrument/statsd.py index e712c47f..5dfe14fa 100644 --- a/gunicorn/instrument/statsd.py +++ b/gunicorn/instrument/statsd.py @@ -81,8 +81,8 @@ class Statsd(Logger): request_time is a datetime.timedelta """ Logger.access(self, resp, req, environ, request_time) - duration_in_s = request_time.seconds + float(request_time.microseconds)/10**6 - self.histogram("gunicorn.request.duration", duration_in_s) + duration_in_ms = request_time.seconds * 1000 + float(request_time.microseconds)/10**3 + self.histogram("gunicorn.request.duration", duration_in_ms) self.increment("gunicorn.requests", 1) self.increment("gunicorn.request.status.%d" % int(resp.status.split()[0]), 1)