When using relative monitoring with the daily pattern we see when the value gets to lower values we get a lot of alarms (see the first screenshot). This is typical that during nighttime fewer devices are active (people are sleeping) and the number of devices during the night can vary much more than over the day. Next to this 90% of 10 (avg number of devices over x days during that 15min) is 9 devices, while the 90% of 200 devices are 180 devices, this means that during the night we can actually have less deviation that can occur on the number of devices compared to overday.
What is the best way to configure relative monitoring and avoid the alarms during nighttime, but still see anomalies like shown in the second screenshot?
Hi Michiel. Can't you work with two alarm templates that you activate via scheduler? Then you could create an alarm template for during the night, and another template for during the day, that can have different thresholds.
After some testing, working with an alarm template group containing both templates (for day and night) with a schedule seem the way forward.
If this is a setup with a lot of devices, like an EPM setup, then you might want to verify the SLElement load at the time of switching the alarms if that isn’t taking up a lot of resources for a few minutes as that could have a negative impact on the other users of the system at that time when they try to access the data.
Hi Tom,
Indeed using an automation script through the scheduler to assign different templates during day and night time is one of the options.
There is also the option to use alarm template groups that have a different schedule, but not a 100% sure (yet) if this would work as expected.