We have a use case to configure an alert on the number of sessions and trigger the alert in case within 5 minutes/interval from 10 AM to 3 PM number of sessions are <500 during working days e.g. Sunday to Thursday.
As a financial institute our business hours setting is below to make sure 24/7 monitoring:
As we aware about the following:
So in the above situation what should we do?
My understanding is, that your need is to limit alerts triggering to Sunday-Thursday 10AM-3PM without Business Hours settings change, is that correct?
I'm afraid it is not doable in 17.0.x and older versions, at least I can not figure out way how to do it. But you may find 2018 release as a solution. In this release we will significantly increase list of dimensions available in alerts mechanism, with "Hour of the day" and "Day of the week" among them . The simplest solution seems to be adding dimension "Hour of the day" with filter 10|11|12|13|14 as a filter. Of course similar way you will be able limit alerts triggering only to Sunday-Thursday using "Day of the week" dimension as a filter
Another thing that I would like to make sure - as number of sessions you mean metric User sessions, am I right? Good news is that this metric is available in alerts mechanism in both, 2017 and 2018 releases.
just tried with 2018 to filter on "Day of the week" and "Hour of the day" together with any other dimension. This seems to be possible only if one alerts on fixed values. I wanted to do a deviation from the relative baseline. Then I get the error message:
"This combination of dimensions is not possible: DMI error. Remove some dimensions/metrics from the alert definition."
I need to admit that you're right, you can not create alerts including Day of the week and Hour of the day dimensions and baseline based conditions at the same time. This is an area of our system which needs to be improved, thank you for pointing it out.
Since analysis how to deal with the problem, how to make solution flexible and universal are still in progress, I can't share more details (especially answer for question when will such alerts be supported). All I can say now is, that I put the issue on the list of topics to fix in upcoming service pack(s) for 2018 release.
I will share more details as soon as they are available