Ticket #27 (new enhancement)
Opened 4 years ago
Rate calculations in rules
| Reported by: | chris | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: |
Description
Request submitted by Dougal Scott:
Quite often I need to put in checks to make sure that the rate of change in a number is within certain limits - lots of things use SNMP style counters for critical data.
Has anyone developed an easy way to get a rate calculation out of eddie? You can do a really rough one based on 'foo-history[1].foo'. This however isn't easily adaptable or accurate. The scanperiod isn't followed to the second so simple diffs aren't accurate. If you change the scanperiod you have to recalculate the numbers in the rules. Also what happens when you use numchecks to really make sure?
What I would like is an internal function, probably called 'rate()' that does all this calculation for you so you could just go 'rate(foo)>5' and it would calculate the rate of foo per second based on the history and the time of the last sample.
