<![CDATA[E-mail notificaiton only for new alarms]]>Hi Victor,

Problem:
Due to technical failure, one of the network devices started sending SNMP traps to NetXMS every couple of seconds with information's about problem.
NetXMS is configured to generate an alarm and one of the actions is to send an e-mail to the group of technicians.
As a result NetXMS generated hundreds of emails during a very short period of time.

Question:
How we can limit number of e-mail send by NetXMS in relation to one alarm?
Could we send email only when new alarm is created and not for subsequent alarms with the same key?

Best regards,
Marcin

]]>https://forum.netxms.org/topic/3872/e-mail-notificaiton-only-for-new-alarmsRSS for NodeFri, 13 Nov 2026 07:23:51 GMTWed, 08 Jul 2015 06:20:17 GMT60<![CDATA[Reply to E-mail notificaiton only for new alarms on Wed, 08 Jul 2015 14:19:17 GMT]]>Thank you for a quick answer.

Could we send email only when new alarm is created and not for subsequent alarms with the same key?
I assume it's not possible.

Is there a better way than using a Situation Manager and storing there timestamp of the event:
processing rule: SetEventParameter($event, "eventtimestamp", $event->timestamp);
situation attribute: %<eventtimestamp>
and then comparing for each event stored timestamp by using FindSituation with current timestamp?

"store timestamp of first event in node's custom attributes" - is it the same procedure as I described above?

Best regards,
Marcin

]]>https://forum.netxms.org/post/17274https://forum.netxms.org/post/17274Wed, 08 Jul 2015 14:19:17 GMT<![CDATA[Reply to E-mail notificaiton only for new alarms on Wed, 08 Jul 2015 12:03:52 GMT]]>Hi,

you can use scripting to store timestamp of first event in node's custom attributes, and for each subsequent event chech if it is too close to original one and only pass through if interval between them is sufficiently large.

Best regards,
Victor

]]>https://forum.netxms.org/post/17266https://forum.netxms.org/post/17266Wed, 08 Jul 2015 12:03:52 GMT