At a base level,
NPM and Core thresholds are locked into just static values. See below, where the only options are:
- what level (integer)
- how do we do capacity planning (boolean)
Yet if you go to any node or interface, you have complex conditions such as:
I also note that 3 TYPES of thresholds are completely off:
1: Disk thresholds (there are large and small disks)
2: Interface thresholds for (receive and transmit utilization)
3: Interface discards
What we need for these and what I'd like to see is very simple
Have:
1: a LARGE THRESHOLD (or maybe an option to add as many as you want) where anything within the LARGE THRESHOLD can be given it's own default criteria
2: a SMALL Threshold (or a conditional, yet again) for what else should have it's own default criteria.
As an example:
<250GB storage: (custom thresholds with actual values)
>250GB and < 4TB storage (custom thresholds)
3: >4TB storage (custom thresholds definition (hard values in specifiable drop down thresholds) - IE: I want to alert when less than 500 (MB/GB/TB/PB)
Most of us end up doing all of this by hand via manage nodes or script it, but it would be good for folks who aren't even scripting yet to have such an option
