Monitoring with Prometheus 2.0
Monitoring with Prometheus 2.0
Posted Jan 18, 2018 10:12 UTC (Thu) by aowi (subscriber, #112529)Parent article: Monitoring with Prometheus 2.0
You can have munin use arbitrary data retention with the "graph_data_size custom" setting though it doesn't seem to be well documented.
https://github.com/munin-monitoring/munin/blob/ce9e01172a...
This is the default retention we use, which keeps five minute samples for two days (5m*576), 30 minute samples (5m*6) for nine days (30m*432) et cetera up to a 1d (5m*288) sampling for ten years (1d*3660):
graph_data_size custom 576, 6 432, 24 540, 288 3660
Posted Jan 18, 2018 16:03 UTC (Thu)
by anarcat (subscriber, #66354)
[Link] (2 responses)
but yeah, 10 years is a timespan i'd like to see...
Posted Jan 18, 2018 17:27 UTC (Thu)
by ken (subscriber, #625)
[Link]
I was adding support to read out temperature from multiple temp sensors using a tellstick duo and then it would be nice to see multiple years but in the end I could not figure out how to do it.
Have not had time to research what to use instead but Prometheus do not look to be the proper solution.
Posted Jan 25, 2018 9:22 UTC (Thu)
by aowi (subscriber, #112529)
[Link]
We're not auto-generating the ten-year graphs, but then again, we're also not auto-generating the three-month graphs, or the 'what happened between 18:00 and 18:30 last Tuesday'-graphs either. But the data is there, and the graphs are three mouse-clicks away when needed. As a tool for exploration, for planning and for the occasional reporting it's quite serviceable.
If you do need to auto-generate the graphs for your purposes, then it'd require a bit more work, yes.
Monitoring with Prometheus 2.0
Monitoring with Prometheus 2.0
Monitoring with Prometheus 2.0