diff --git a/doc/source/admin/special_topics/performance_tracking.rst b/doc/source/admin/special_topics/performance_tracking.rst index ecd5aed2103..e500cca698b 100644 --- a/doc/source/admin/special_topics/performance_tracking.rst +++ b/doc/source/admin/special_topics/performance_tracking.rst @@ -8,7 +8,7 @@ Most performance tracking requires sending metrics to a metrics collection serve uWSGI ----- -As you have certainly switched to uWSGI from the default paste server, there is some built-in uWSGI support for performance logging. You can send uWSGI's internal metrics to a carbon (Graphite) server by setting the carbon option in your galaxy.yml: +There is some built-in uWSGI support for performance logging. You can send uWSGI's internal metrics to a carbon (Graphite) server by setting the carbon option in your galaxy.yml: .. code-block:: yaml @@ -20,11 +20,26 @@ Or a StatsD server via: .. code-block:: yaml - wsgi: + uwsgi: socket: ... - statsd-push: 127.0.0.1:8125 + stats-push: statsd:127.0.0.1:8125 -The `official documentation `__ contains further information on uWSGI and stats servers. In the `uWSGI Stats Server ` documentation, you can see an example of the sort of information that you will be able to collect. +The `official documentation `__ contains further information on uWSGI and stats servers. In the `uWSGI Stats Server `__ documentation, you can see an example of the sort of information that you will be able to collect. Note that you will need to make sure that the statsd pusher plugin is activated in your uWSGI servers. + +Alternatively, you can use `gxadmin `__ to generate data ready to load in an InfluxDB database. In this case, you will need to add the stats option to your galaxy.yml: + +.. code-block:: yaml + + uwsgi: + socket: ... + stats: 127.0.0.1:9191 + +And then run gxadmin like this: + + +.. code-block:: bash + + gxadmin uwsgi stats_influx 127.0.0.1:9191 API / Route Timing Statistics -----------------------------