<?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[Alert Configuration]]></title><description><![CDATA[<p dir="auto">Thanks very much for the utility.  We're trying to make this solution part of our network monitorning.  We have the following questions:</p>
<ol>
<li>
<p dir="auto">How do we disable alerts and notifications of a sys_node_down\sys_node_up status during a set time period?  For example, during the 12am to 4am hours, the majority of our servers go through a restart process.  How do we configure the scheduling so that the email notification of sys_node_down and sys_node_up are not captured over a certain time period?</p>
</li>
<li>
<p dir="auto">How do we configure the email alerts to only send once email every 5 minutes and stop after 4 emails when a sys_node_down event occurs.  In other words, we've created an event processing policy for sys_node_up and sys_node_down for sending an email notification once when an event occurs.  How do we create an email event so that we are notified once every 5 minutes with a max of 4 emails?</p>
</li>
</ol>
<p dir="auto">Thanks in advance.</p>
<p dir="auto">Aron</p>
]]></description><link>https://forum.netxms.org/topic/770/alert-configuration</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 09:21:39 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/770.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 16 Nov 2009 22:17:25 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Alert Configuration on Tue, 17 Nov 2009 08:36:47 GMT]]></title><description><![CDATA[<p dir="auto">Hello!</p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/aron-schneider" aria-label="Profile: aron-schneider">@<bdi>aron-schneider</bdi></a> said in <a href="/post/3615">Alert Configuration</a>:</p>
<blockquote>
<ol>
<li>How do we disable alerts and notifications of a sys_node_down\sys_node_up status during a set time period?  For example, during the 12am to 4am hours, the majority of our servers go through a restart process.  How do we configure the scheduling so that the email notification of sys_node_down and sys_node_up are not captured over a certain time period?</li>
</ol>
</blockquote>
<p dir="auto">You can achieve this by adding additional filtering script to the rule. Script for checking if current time is not between 00:00 and 04:00 (04:00 not included) may look like following:</p>
<pre><code>sub main()
{
   now = localtime();
   return now-&gt;hour &gt;= 4;
}
</code></pre>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/aron-schneider" aria-label="Profile: aron-schneider">@<bdi>aron-schneider</bdi></a> said in <a href="/post/3615">Alert Configuration</a>:</p>
<blockquote>
<ol start="2">
<li>How do we configure the email alerts to only send once email every 5 minutes and stop after 4 emails when a sys_node_down event occurs.  In other words, we've created an event processing policy for sys_node_up and sys_node_down for sending an email notification once when an event occurs.  How do we create an email event so that we are notified once every 5 minutes with a max of 4 emails?</li>
</ol>
</blockquote>
<p dir="auto">There are no easy way to achieve this. However, you can try the following:</p>
<ol>
<li>Create custom event, like NODE_STILL_DOWN;</li>
<li>In processing policy, add action that runs a script on server; this script should run nxevent tool four times to post NODE_STILL_DOWN event to server four times with 5 minutes interval, and then exit;</li>
<li>Add event processing policy rule for NODE_STILL_DOWN event - it should check if node is still down and if yes, send additional email.</li>
</ol>
<p dir="auto">Hope this helps!</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/3616</link><guid isPermaLink="true">https://forum.netxms.org/post/3616</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Tue, 17 Nov 2009 08:36:47 GMT</pubDate></item></channel></rss>