Hi all,
I am trying to have a delay on some alarms with \"HYST OFF\" as for DM to keep the alarm in there at least 60 s regarding some of them flapping for 15 - 40 s as a example.
I have the alarm template as you can see:
And I do not get the required behavior.
I am using a variant of a generic trap receiver driver in which I am alarming on incoming traps with critical as value and also receive clear traps in the same table.
Time between Critical and Clear some time is less then 60s which is mandatory for me in order to create Tickets in SNOW.
You can see as example the firs alarms where present only for a few second (more than 10) and I would expect them to be there at least 60 s.
The table in which i am collecting critical traps(with red) and when the clear trap is is, the specific row is modified from critical to clear (green).
Can you please advise, maybe I am missing something.
Thank you
Catalin
Hi Catalin,
When you are using Hysteresis ON, (and the alarm lasts longer than the hysteresis) the alarm will have the timestamp when the trap came in (so not the time after the hysteresis).
The same happens for hysteresis off, the normal alarm will have the timestamp of when clear trap came in (if no new alarm trap came in in the hysteresis time).
This can cause alarms in the alarm console that are shorter than your hysteresis time.
What you should not see, is multiple alarms of the same index having a normal alarm, end a critical alarm within your hysteresis time. I can't spot such a case in your alarm console, so the hysteresis seems to be working as expected.
You can add the “Creation Time” column to the alarm console. If this is different from the “Time” column, it’s because a hysteresis was applied.
Hi and thank you. It is any possibility to check if the alarm was shown in the alarm console for the time of hyst of ?