Check the impact when setting alarm conditions on the time axis in the event settings

[MARUBUN SUPPORT]

Hi Team,

OS：RHEL7.2
Spectrum 24.3.9 

If I set a time-based alarm condition for an event, is there any difference in normal processing compared to when I don't set an alarm condition?

For example, continuing to allocate memory space.
I'm planning to add a condition that will generate a new alarm (new event) if a certain event is detected twice within 12 hours.
In this case, I'll need to retain the detected alarm for 12 hours, but I'd like to confirm that this will not affect the system.

Also, could you please let me know if there are any manufacturer-recommended values for the time-based threshold?

Thanks,

[Robert Kettles]

Hello,

I'm not sure I understand the question.  All active alarms consume memory in the system.  For a single alarm, it's generally negligible.  The issue is when you start getting tens of thousands of alarms that performance gets impacted.  It also gets unusable from an operations perspective for most NOCs. 

-Rob