I have a case where a user configured an alarm template to have 1200 seconds of hysteresis On and Off.
However, the results aren't the expected ones. As you can see in the picture, the parameter surpasses the threshold longer than the Hyst ON is set to, but the alarm never reaches the console. and when the parameter is normal, the critical state is never removed:
If they remove the Hyst ON and OFF, the alarms and their state are displayed according to the parameter value.
So I'm wondering:
- Is there any restriction on the time limit for the Hysteresis configuration?
- Should/can a user configure both?
- Is there any negative impact on the system to enable this Hysteresis in big tables with many rows (routers, CMTS, etc.)?
Thanks!
Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 11th July 2023
Arturo, to answer your 3 questions
- There is no built-in limit on the time you can specify as hysteresis. In your case 20 minutes should work fine.
- Yes, as a user you can configure both the on and off hysteresis
- The size of the table has no immediate impact on the hysteresis. It is mainly the number of active 'count-downs' being executed that might have an impact. Technically, DataMiner schedules an event within the configured time to re-evaluate the value at that moment.
We'll need to further investigate your particular case where the alarm is incorrectly created and cleared.
Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 11th July 2023