From d2610dc4830c89fd4d8418499ef060fd5f110b0b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alexis=20L=C3=AA-Qu=C3=B4c?= Date: Mon, 12 May 2014 18:31:37 +0200 Subject: [PATCH] Cosmetic cleanup --- README.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.rst b/README.rst index 1ad7fbed..00c4a433 100644 --- a/README.rst +++ b/README.rst @@ -159,13 +159,13 @@ To use this instrumentation mechanism, simply use a new logger:: The `Statsd` logger overrides `gunicorn.glogging.Logger` to track all requests. The following metrics are generated: - * `gunicorn.requests`: request rate per second - * `gunicorn.request.duration`: histogram of request duration - * `gunicorn.workers`: number of workers managed by the arbiter (gauge) - * `gunicorn.log.critical`: rate of critical log messages - * `gunicorn.log.error`: rate of error log messages - * `gunicorn.log.warning`: rate of warning log messages - * `gunicorn.log.exception`: rate of exceptional log messages + * ``gunicorn.requests``: request rate per second + * ``gunicorn.request.duration``: histogram of request duration + * ``gunicorn.workers``: number of workers managed by the arbiter (gauge) + * ``gunicorn.log.critical``: rate of critical log messages + * ``gunicorn.log.error``: rate of error log messages + * ``gunicorn.log.warning``: rate of warning log messages + * ``gunicorn.log.exception``: rate of exceptional log messages To generate new metrics you can `log.info` with a few additional keywords::