We are monitoring the CPU of some remote servers on Sitescope 11.24, and using the HP Integration Settings to send the monitor results to BSM 9.25, and we use CI status alerts on BSM to notify of error conditions through email (this last part is standard practice in our environment and not specific to only these CPU monitors), as well as the followup back-to-good condition.
Since we can't control the status of the Sitescope monitor depending on the time it's been on an specific state, what we have done so far is just get whatever status it sends and then configure the CI status alerts to only send the email if the CI has been on a certain state for over 10 minutes.
This is certainly not optimal, on one hand because the "send alert if status is equal or worse than warning for 10 minutes" doesn't seem to send any email ever even when it's been on error for almost half and hour, but also because we would be getting followup back-to-good emails even if the "worse than warning for 10 minutes" alert condition wasn't ever met.
I guess the correct approach would involve using Sitescope alerts, where we can configure how many times a condition must be met before triggering the alert, but I'm not sure about how to implement that with SiS-BSM.
If I configure a Trigger alert action then that should generate an event when the Status Trigger and Trigger Frequency are matched by the monitor status, but how does that work with BSM? Do I need to configure a specific setting in Sitescope's HP Integration Settings so that only events generated through this SiS alert impact on the CI?
PS: we don't have OMi (which is why I'm finding the use of alert events confusing).