200+ check plugins for Icinga and other Nagios-compatible monitoring applications. Each plugin is a standalone command line tool (written in Python) that provides a specific type of check.
With Continous Counters (unit "c") we have major disadvantages with regard to software like Grafana:
Assume rendering a panel based on data for the last two years which was gathered once per minute. This means at least 1.1M measurements for one perfdata-item, or 15.8M measurements for 15 perfdata-item, and so on.
To speed up a panel, Grafana has to aggregate values (for example by using mean()). For c-values, the calculated values are obviously wrong.
With c-values, you can't design some meaningful and performant tables showing min(), max(), first(), last() or mean() values.
c-values are missing any furter unit of measurements. You don't know if it's byte, percentage or second.
Efficiency at all: Why always calculate the difference between two c-values in Grafana & Co. if this could be done by the monitoring plugin only once while gathering the data? This saves resources on the monitoring server.
This leads to:
Convert all continous counters to absolute values.
Never use continous counters at all.
After that, in all Grafana Panels dealing with c-values:
In GitLab by @markuslf on Jul 23, 2021, 16:23
With Continous Counters (unit "c") we have major disadvantages with regard to software like Grafana:
This leads to:
After that, in all Grafana Panels dealing with c-values: