<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Timed Alarms Configuration]]></title><description><![CDATA[<p dir="auto">My goal is to have three alarms when a node goes down. One alarm after being down for 2 min, another alarm after being down 5 minutes, and a third alarm once the node has been down for 20 minutes. </p>
<p dir="auto">Once the node comes back on line then we get a node Up alert.</p>
<p dir="auto">With my current setup this is all working with one snag. If a node goes down for less than 2 minutes and then comes back up I get a node up alert. Since the node was down for less than 2 minutes I never get the node down alert. </p>
<p dir="auto">Very similar to the issue in this post from 2012, but when I try to add the first script Netxms tells me its deprecated. <br />
<a href="https://www.netxms.org/forum/general-support/event-based-on-resolving-an-alarm-timeout/" rel="nofollow ugc">https://www.netxms.org/forum/general-support/event-based-on-resolving-an-alarm-timeout/</a></p>
<p dir="auto">I'm not familiar with scripting at all so I was hoping I could get this accomplished using some combo of event processing policies. Any help would be appreciated.</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000006785-EPP.jpg" alt="EPP.jpg" class="img-markdown  img-fluid" width="1372" height="555" /></p>
]]></description><link>https://forum.netxms.org/topic/8042/timed-alarms-configuration</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 07:21:39 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/8042.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 11 Oct 2024 15:19:32 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Timed Alarms Configuration on Wed, 16 Oct 2024 19:17:50 GMT]]></title><description><![CDATA[<p dir="auto">That was exactly what I needed. Thanks! Posting setup here for reference.</p>
<p dir="auto">Node goes down.<br />
2 minutes later slack alert goes out<br />
5 minutes later slack alert goes out<br />
20 minutes later slack alert goes out</p>
<p dir="auto">If the node comes up prior to 2 minute alert, alarms are cleared and no alert is sent. </p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000006791-10-16-2024_2-15-56_PM.jpg" alt="10-16-2024 2-15-56 PM.jpg" class="img-markdown  img-fluid" width="1379" height="702" /></p>
]]></description><link>https://forum.netxms.org/post/33909</link><guid isPermaLink="true">https://forum.netxms.org/post/33909</guid><dc:creator><![CDATA[redlam]]></dc:creator><pubDate>Wed, 16 Oct 2024 19:17:50 GMT</pubDate></item><item><title><![CDATA[Reply to Timed Alarms Configuration on Wed, 16 Oct 2024 11:52:09 GMT]]></title><description><![CDATA[<p dir="auto"><img src="/assets/uploads/files/smf/0000000006789-rules_up_down.jpg" alt="rules_up_down.jpg" class="img-markdown  img-fluid" width="2760" height="1413" /></p>
]]></description><link>https://forum.netxms.org/post/33901</link><guid isPermaLink="true">https://forum.netxms.org/post/33901</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 16 Oct 2024 11:52:09 GMT</pubDate></item><item><title><![CDATA[Reply to Timed Alarms Configuration on Wed, 16 Oct 2024 11:50:48 GMT]]></title><description><![CDATA[<p dir="auto">Screenshot below shows how we do it. Basic idea is not to send "node up" notification if timer for "node down" notification was not fired yet. Note that rule order is important in this setup.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/33900</link><guid isPermaLink="true">https://forum.netxms.org/post/33900</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 16 Oct 2024 11:50:48 GMT</pubDate></item></channel></rss>