From d08ce52cce71214ed8812169f8051603b75626d3 Mon Sep 17 00:00:00 2001 From: Anthony Bretaudeau Date: Mon, 4 Mar 2019 12:20:03 +0100 Subject: [PATCH 1/4] Fix doc for statsd conf for uwsgi --- doc/source/admin/special_topics/performance_tracking.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/admin/special_topics/performance_tracking.rst b/doc/source/admin/special_topics/performance_tracking.rst index ecd5aed2103..e512f0bd0bf 100644 --- a/doc/source/admin/special_topics/performance_tracking.rst +++ b/doc/source/admin/special_topics/performance_tracking.rst @@ -22,7 +22,7 @@ Or a StatsD server via: wsgi: 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. From 3a220d02b9c3e6c1f178de9f579a248ff0993cfe Mon Sep 17 00:00:00 2001 From: Anthony Bretaudeau Date: Mon, 4 Mar 2019 15:26:11 +0100 Subject: [PATCH 2/4] typo --- doc/source/admin/special_topics/performance_tracking.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/admin/special_topics/performance_tracking.rst b/doc/source/admin/special_topics/performance_tracking.rst index e512f0bd0bf..e123c0e65f3 100644 --- a/doc/source/admin/special_topics/performance_tracking.rst +++ b/doc/source/admin/special_topics/performance_tracking.rst @@ -20,7 +20,7 @@ Or a StatsD server via: .. code-block:: yaml - wsgi: + uwsgi: socket: ... stats-push: statsd:127.0.0.1:8125 From ba2e0240fe4449dc8c6c19d40b69d3d1f1451c2f Mon Sep 17 00:00:00 2001 From: Anthony Bretaudeau Date: Mon, 4 Mar 2019 15:34:16 +0100 Subject: [PATCH 3/4] add details on gxadmin --- .../special_topics/performance_tracking.rst | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/doc/source/admin/special_topics/performance_tracking.rst b/doc/source/admin/special_topics/performance_tracking.rst index e123c0e65f3..710cbf8610f 100644 --- a/doc/source/admin/special_topics/performance_tracking.rst +++ b/doc/source/admin/special_topics/performance_tracking.rst @@ -24,7 +24,22 @@ Or a StatsD server via: socket: ... 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 ----------------------------- From 0156e61a585e9d8b431b4d5ec30269e247ff929a Mon Sep 17 00:00:00 2001 From: Anthony Bretaudeau Date: Mon, 4 Mar 2019 16:46:56 +0100 Subject: [PATCH 4/4] remove reference to paster --- doc/source/admin/special_topics/performance_tracking.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/admin/special_topics/performance_tracking.rst b/doc/source/admin/special_topics/performance_tracking.rst index 710cbf8610f..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