Add time-based logic to NPM thresholds like SAM v.6.1.1

klinejw

Add time-based/number of poll logic to NPM thresholds like you introduced in SAM 6.1.1 so that you can assign a threshold for 'a single poll', 'x consecutive polls', or 'x out of y polls'.  I know that I can accomplish this via the advanced alert manager via a custom SQL alert, but it would be nice to have native support for this out of the box.

xtraspecialj

Here here!  We try to have only one type of alert for each type of object in Orion (so 1 Node Down alert, 1 Interface Down alert, 1 Node High Response Time Alert, etc...).  When building an alert we point the Trigger/Reset Conditions at Thresholds instead of static numbers (so an alert would never have a Trigger Condition like "Interface Transmit Utilization Greater than 90%", instead it would say "Interface Transmit Utilization Greater Than Critical Threshold"), but the problem with this in every product except for SAM is that if you only want to alert when over the threshold for longer than 20 minutes on some interfaces but longer than 60 minutes on other interfaces you end up having to create two alerts, ruining the whole plan.

I would extend this feature request to ALL Orion Products.  Every single Threshold in every single Orion module should have the same time-based features as SAM thresholds have.  I mean, who cares if traffic spikes on an interface 1 time or if the CPU usage of a server goes higher than 90% for 1 polling cycle?  Almost nobody...  But the problem is different teams may have different desires on the how long plan, and being able to set that at the individual threshold level is far superior than having to create an entire new alert just to serve the needs of one team at your company.  You could potentially end up with dozens of alerts for each type of thing if you are doing that, and a lot of alerts is a nightmare to administer.