Skip to content
This repository has been archived by the owner on Oct 6, 2023. It is now read-only.

Enhancement request - AVERAGE vs LAST value in RRD #140

Open
ponsn opened this issue Nov 8, 2017 · 0 comments
Open

Enhancement request - AVERAGE vs LAST value in RRD #140

ponsn opened this issue Nov 8, 2017 · 0 comments

Comments

@ponsn
Copy link

ponsn commented Nov 8, 2017

Good morning, this isn't a bug but an enhancement request instead.

Would it be possible to have the LAST value stored in the RRD instead of AVERAGE ?

The idea is to show the real data instead of computed ones, which can often be misleading.
A typical example is: a server standard CPU load is between 0-10%. At a given time, for any reason, the CPU load reaches 100% for a few minutes. Enough to be caught by a check, and centreon may notify the users (or not), but the graph will store that value and average it with the previous ones showing a pick at 25ish% (let say, 5% + 5% + 5% + 100%).

Ideally, I believe this should be an user configurable value, which I understand may require quite some effort in implementing.
I am also conscious it might induce a RRD file size increase according the user retention settings and the quantity of host/services having perfdata being graphed: therefore, I propose the default value to be AVERAGE, so it does not harm any other existing installations.

Thanks for your feedback.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant