Perhaps I am just misunderstanding the concept behind Status over Time but I set a KPI to trigger if it is at Critical 90% of the time for the last 24 hours and when I open it to set that 90% (see screenshot) it shows that in the last 24 hours it was WELL below 90% but this notable event triggers over and over again non-stop almost.
Am I misunderstanding the concept behind an alert that triggers if the KPI is at Critical 90% of the last 60 mins?
I am assuming you want to have the Notable Event when the condition has been Critical for ~21.5 hours of a 24 hour period. From your description that seems to be correct.
The real trouble with the multi-kpi editor seems to be related to a bug when it creates the actual search syntax. To see what I mean, click on the search you have created under the 'Correlation Searches' menu item under 'Configure'
Under "Actions' click Edit 'by Correlation Search Editor'.
Open that search by clicking 'Run Search' under the "Search" box.
Notice the line that says
| stats count as occurances latest(*) as * by alertseverity itsikpiid itsiservice_id
occurances is spelled with an "a", but later a macro is called with a parameter of occurrence
That value doesn't exist.
That macro expands and is indeed looking for a value that would have been provided by the occurances variable created in the earlier stats statement, and additionally is core to the whole point of your intended multi-kpi search.
I have gotten around this by editing the search syntax and adding the statement
right after the stats statement that created the occurances variable.
Lets this run and I believe this will resolve your constant alerting condition.
Hope this was clear, feel free to ask for clarification.
Hi guys, thanks a lot for finding this. I've filed a bug and it should be fixed in the next ITSI release.