Hello dovecot list,
I'm in the middle of creating a plugin for observium1 and would like to have it create2 statistical graphs of my dovecot server 3. The current state can be found here: https://image.ibb.co/efOO9a/dovecot.png
However for visibility purposes it doesnt make sense and have observium plot two data sources with different orders of magnitudes right into one graph. So I'd like to ask for your valuable recommendations as for:
What kind of data should be graphed? Global stats or on a per domain level?
What data types to graph? (e.g. stats, getrusage, io, storage, auth check https://wiki2.dovecot.org/Statistics#line-65 for details)
What values should be combined into a single graph?
How often would you reset stats (cronjob calling doveadm stats reset)?
Thanks Thomas
On July 15, 2017 at 8:59 PM Thomas Reifferscheid <thomas@reifferscheid.org> wrote:
Hello dovecot list,
I'm in the middle of creating a plugin for observium[1] and would like to have it create[2] statistical graphs of my dovecot server [3]. The current state can be found here: https://image.ibb.co/efOO9a/dovecot.png
However for visibility purposes it doesnt make sense and have observium plot two data sources with different orders of magnitudes right into one graph. So I'd like to ask for your valuable recommendations as for:
What kind of data should be graphed? Global stats or on a per domain level?
What data types to graph? (e.g. stats, getrusage, io, storage, auth check https://wiki2.dovecot.org/Statistics#line-65 for details)
What values should be combined into a single graph?
How often would you reset stats (cronjob calling doveadm stats reset)?
Thanks Thomas
Hi!
Just thought I'd remind about few things,
since v2.2.22 you can use doveadm -fjson, to print data in json format, which might be easier to parse.
since v2.2.22 you can use doveadm HTTP API to get the statistics over HTTP.
since v2.2.27 you can export stats to remote server every now and then using carbon format.
Aki
Am 15.07.2017 um 20:26 schrieb Aki Tuomi:
Hi! Just thought I'd remind about few things,
since v2.2.22 you can use doveadm -fjson, to print data in json format, which might be easier to parse.
As for Debian stable (dovecot 2.2.27) -f json is missing from the manpage.
since v2.2.22 you can use doveadm HTTP API to get the statistics over HTTP.
since v2.2.27 you can export stats to remote server every now and then using carbon format.
Aki
Hi Aki
I've been changing the data types from GAUGE to COUNTER for all input data but not for the num_connected_sessions - keeping GAUGE here. The result can be found here:
https://image.ibb.co/krSHkF/dovecot1.png https://image.ibb.co/cdTZXv/dovecot2.png https://image.ibb.co/csHHkF/dovecot3.png
I'll let the observium guys review the scripts unless somebody else has any suggestions or comments.
Thomas
Hi,
interesting scripts, any plans to support libreNMS too or are there license issues?
regards,
Harald
Am 16.07.2017 um 00:12 schrieb Thomas Reifferscheid:
Am 15.07.2017 um 20:26 schrieb Aki Tuomi:
Hi! Just thought I'd remind about few things,
since v2.2.22 you can use doveadm -fjson, to print data in json format, which might be easier to parse.
As for Debian stable (dovecot 2.2.27) -f json is missing from the manpage.
since v2.2.22 you can use doveadm HTTP API to get the statistics over HTTP.
since v2.2.27 you can export stats to remote server every now and then using carbon format.
Aki
Hi Aki
I've been changing the data types from GAUGE to COUNTER for all input data but not for the num_connected_sessions - keeping GAUGE here. The result can be found here:
https://image.ibb.co/krSHkF/dovecot1.png https://image.ibb.co/cdTZXv/dovecot2.png https://image.ibb.co/csHHkF/dovecot3.png
I'll let the observium guys review the scripts unless somebody else has any suggestions or comments.
Thomas
-- Harald Leithner
ITronic Wiedner Hauptstraße 120/5.1, 1050 Wien, Austria Tel: +43-1-545 0 604 Mobil: +43-699-123 78 4 78 Mail: leithner@itronic.at | itronic.at
Am 16.07.2017 um 00:12 schrieb Thomas Reifferscheid:
[...]
I'll let the observium guys review the scripts unless somebody else has any suggestions or comments.
The observium feature ticket can be found at http://jira.observium.org/browse/OBSERVIUM-2347
Thomas
participants (3)
-
Aki Tuomi
-
Harald Leithner
-
Thomas Reifferscheid