Compound Incidents using 'or'
We have been implementing incidents attempting to use the 'or' function to trigger the incidents based upon multiple measures/thresholds.
However, after we noticed some incidents didn't fire correctly, we found that the 'or' seems to be ignored and the incident only triggers on one of the measures/thresholds.
Has anyone seen similar or have seen it working?
A couple examples of when we would like to use compound incidents are:
- Apache busy threads are too high or idle threads are too low.
- DB Time is too high or JDBC pool usage it too high
Thanks
Brad
You're saying you already have these set up and they're not working? Can you show your configurations here, including the measures you use as conditions?
Rick B
Brad,
The DB Time measure measures the performance of individual database requests. You have set a threshold of 40 seconds, which is pretty high for a single database request.
Have you graphed this measure – with "Show Thresholds" checked – and seen the value exceed 40 seconds?
Also, I'm assuming you've set the aggregation method in the incident definition to 'max'?
-- Graeme
We have observed the incident will only trigger when the DB Time measure breaches it's threshold while we can observe that the Pool Usage measure is well over 90%.
I added the measure to a newly created incident with just that measure and it triggered right away.
Graeme,
Yes this app makes long SQL calls so we had to set the measure high.
Brad
