<?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[Alarming on Windows Events]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">another topic that I try to wrap my head around. I'm trying to get alarms on different windows events. For the moment I just want a warning message.</p>
<p dir="auto">So, I have configured Windows Event Log to be pushed to NetXMS server. Does work.<br />
I have configured the Windows Event Parser like this:</p>
<pre><code>&lt;parser trace="0" name="WindowsEventLog"&gt;
   &lt;macros/&gt;
   &lt;rules&gt;
      &lt;rule name="SQL Login failed"&gt;
         &lt;match repeatInterval="0" reset="false"&gt;(.*)&lt;/match&gt;
         &lt;event&gt;WIN_EVENT_RECORD_MATCHED&lt;/event&gt;
         &lt;id&gt;18456&lt;/id&gt;
         &lt;logName&gt;Application&lt;/logName&gt;
         &lt;agentAction action=""&gt;&lt;/agentAction&gt;
      &lt;/rule&gt;
      &lt;rule name="SQL Login failed"&gt;
         &lt;match repeatInterval="0" reset="false"&gt;(.*)&lt;/match&gt;
         &lt;event&gt;WIN_EVENT_RECORD_MATCHED&lt;/event&gt;
         &lt;id&gt;18452&lt;/id&gt;
         &lt;logName&gt;Application&lt;/logName&gt;
         &lt;agentAction action=""&gt;&lt;/agentAction&gt;
      &lt;/rule&gt;
   &lt;/rules&gt;
&lt;/parser&gt;
</code></pre>
<p dir="auto">A couple of questions already:</p>
<ul>
<li>The parser is asking for a name, but it seems like you only can have one. So why does it ask for a name and what does the name matter?</li>
<li>For templates you can define Agent Policies and within a Log Parser. The UI looks similar. Is this a place where Windows Event Parser can be defined as well?</li>
</ul>
<p dir="auto">Ok then I defined the Event WIN_EVENT_RECORD_MATCHED with severity of Warning and a message of: Windows event ID %3: "%1"<br />
As I understood the documentation n+2 (= %3) should be the EventID - but it is just empty.</p>
<p dir="auto">Furthermore, in Event Processing Policy I created an alarm with Message "%m" and Alarm key of "WIN_EVT_%i_%3" to group id by Event ID. But as %3 is empty all events from a single machine are merged.</p>
<p dir="auto">What am I doing wrong?</p>
<p dir="auto">Cheers</p>
]]></description><link>https://forum.netxms.org/topic/7115/alarming-on-windows-events</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 09:23:07 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/7115.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 28 Jul 2021 13:41:48 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Alarming on Windows Events on Mon, 02 Aug 2021 06:16:52 GMT]]></title><description><![CDATA[<p dir="auto">Thanks for your reply. Now I understand the different approaches. If you prepend the file path with * the "Event ID" becomes a field that is writable. Missed that before. It seems like you can do more flexible things with the traditional Log Parser.</p>
<p dir="auto">I use the current 3.9.156, but 3.8.something before didn't have the parameters set as well. Maybe if I use the Log Parser instead of the Windows Event Parser?</p>
<p dir="auto">Edit: Yes, indeed. It works if I use the Log Parser out of the Policies. But I guess that's better anyway.</p>
]]></description><link>https://forum.netxms.org/post/30295</link><guid isPermaLink="true">https://forum.netxms.org/post/30295</guid><dc:creator><![CDATA[2b2bff]]></dc:creator><pubDate>Mon, 02 Aug 2021 06:16:52 GMT</pubDate></item><item><title><![CDATA[Reply to Alarming on Windows Events on Fri, 30 Jul 2021 05:34:47 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">For historical reasons there are two approaches to monitoring windows event logs.</p>
<ol>
<li>
<p dir="auto">Log parser policy in Template. Windows event log is specified in "File path" field prepended by *, e.g. "*System". Parsing is done on agent side. If something matches, agent sends event to server.<br />
This approach allows to specify different templates for different nodes.</p>
</li>
<li>
<p dir="auto">Windows event log syncronization. <a href="https://www.netxms.org/documentation/adminguide/windows-event-log-synchronization.html" rel="nofollow ugc">https://www.netxms.org/documentation/adminguide/windows-event-log-synchronization.html</a><br />
This was developed for a customer, who needed to actually store windows event logs centrally. In agent config some filters are specified to include/exclude logs by some parameters. Then logs are sent to server and stored (storing can be omitted by rule(s) in parser).<br />
When logs arrive at the server, they are parsed according to rules specified in "Windows event parser". These rules are global - it's currently not possible to filter by specific nodes/containers, rules work equally for all arriving events. If something matched, event is generated.</p>
</li>
</ol>
<p dir="auto">Name in Windows parser - just the same code was reused as from policy in template and forgot to hide this field. Name does not affect anything.</p>
<p dir="auto">Parameters in created events were (or should have been) fixed in some specific netxms version. What exactly version are you using?</p>
]]></description><link>https://forum.netxms.org/post/30288</link><guid isPermaLink="true">https://forum.netxms.org/post/30288</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Fri, 30 Jul 2021 05:34:47 GMT</pubDate></item></channel></rss>