Alarm hysteresis not behaving right – it is showing alarms that were active only 2 seconds

Solved417 views
0
1 Comment

Hello Dojo,

I am having a strange situation. I have set some alarms to be sent, using hysteresis. Settings are according to the image below:

But my Appear chassis shows this time stamp:

With hysteresis on, set at 60 seconds, i should get the alarms only after 60 seconds and if they are still there.

Why is Dataminer sending out the alarms without taking into account that hysteresis?

Thanks!

Marian

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 19th July 2023
Marieke Goethals [SLC] [DevOps Catalyst] commented

Hi Marian,
Have you been able to solve the issue with these answers? If so, could you select the best answer (using the ✓ icon)?

2 Answers

2
8.64K 1 Comment

Hi Marian,

Just to make sure that we all talk about the same thing, because you seem to refer to alarms that you see in Appear TV in their web interface: whatever you configure in terms of hysteresis in DataMiner, it will not impact the alarms displayed in Appear TV.  DataMiner retrieves data from Appear TV, it evaluates whether or not there is an alarm based on the Alarm Template configuration, and where necessary it generates an alarm accordingly in the DataMiner Alarm Console.  As Emmanuel indicated, if the data collection is based on polling cycles, then of course there could be delays, and only when the data is retrieved DataMiner can re-evaluate the situation, and updates its alarms in DataMiner accordingly.

Note also that if this revolves around delaying the triggering of an e-mail notification, then you would have two options.  A) you delay the triggering of an Alarm in DataMiner, and then accordingly the e-mail notification will be delayed, or B) you leave the alarms as is, with no hysteresis, but you use a correlation rule to trigger when the alarm is active for a longer period, and to then dispatch an e-mail notification as a result.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 19th July 2023
Marian Bacana commented

Hi Ben,

About AppearTV, that is crystal clear. Dataminer is only reading AppearTV’s status.
Alarm template is pretty simple, having only 7 alarms configured. The goal is to read the interface of AppearTV (this is done correctly but having some delays from time to time), use hysteresis option (60 seconds on, 10 seconds off), and in the end display / send email if conditions are met.
I have set the pooling time (from AppearTV drivers) to 15 seconds.
So at every 15 seconds information is pulled from the equipment. Even so, i get short alarms (1-2 seconds) immediately as they come.
This is something i can check and compare in the web interface. I’ll try to dig more into this by changing values and testing.

Thank you!
1
4.61K 3 Comments

Hi Marian,

It depends on how frequently the connector retrieves the alarms from the AppearTV chassis.

In case they are retrieved each X minutes, an alarm will stay in the console for X minutes at least (minus hysteresis time).

Miguel Obregon [SLC] [DevOps Catalyst] Posted new comment 9th June 2023
Marian Bacana commented

Hi Emmanuel,

It is not a problem how long they stay in the console alarm. The problem is that they are displayed even if i set the hysteresis. And because of this being ignored, i get email alarms.
This is one of the alarms that i get frequently and it only stays on for 1-2 seconds. So my goal is to have Dataminer sending out an email only when the alarm is around for at least 2-3-4 minutes.

Can you indicate a proper setup so i ca get the alarm email when the actual alarm is on AppearTV equipment for at least 3 minutes?
With 60 seconds hysteresis, would be nice.

Thank you!
Emmanuel Dal [SLC] [DevOps Enabler] commented

Let me explain into more details what could maybe happen here. Let’s consider that the alarms are retrieved each 10 minutes (I have no idea if this is the case)

– at 01:27:03 the connector retrieves the alarms
– at 01:32:03 the alarms is generated in the console ( considering the 5 minutes hysteresis)
– at 01:37:03 the connector retrieves the alarms
– at 01:37:13 the alarm is removed from the console ( considering the 10s hysteresis)

So, even if the alarm was present on the device for a very short duration, it was present in DMA for 5 minutes.

I’m not saying this is the case here, however the behavior you’ve described in a different question tend to confirm this (https://community.dataminer.services/question/alarms-are-shown-delayed-in-the-dataminer-cube/ )
Miguel Obregon [SLC] [DevOps Catalyst] commented

Hi Marian,
To troubleshoot this, you could try:
– Disable first the alarmhysteresis.
– Wait for a new alarm incident and check the timestamp in the AppearTV web interface.
– Then check the alarm console in the DMA and check the root time of the alarm related to the same incident.
After this you should able to see how long it takes for the DMA to see the alarm generated by the Appear TV chassis.
The root time of the alarm indicates when the DMA received this alarm. This timestamp is not necessary the same timestamp displayed in the AppearTV web interface.
Hope it helps