<?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[syslog parser rules not working]]></title><description><![CDATA[<p dir="auto">Hi, on ver 2.2.2, I have tried setting up a few syslog parser rules with the editor for the internal syslog.</p>
<p dir="auto">I have one successfully working rule (looking at logins to a synology DSM).  However any rule I've added since (one for VPN logins and one for unifi time sync) does not seem to generate an event in the event log. <br />
Have tried:</p>
<ul>
<li>altering the order of the rules</li>
<li>click process all</li>
<li>look at a level 9 debug (the syslog is being seen and added to the database but no EVENT is generated).</li>
<li>restarting the server</li>
<li>The custom events are configured to write to the event log</li>
</ul>
<p dir="auto">Is there an error in my regex?</p>
<pre><code>&lt;parser trace="9"&gt;
   &lt;file/&gt;
   &lt;rules&gt;
      &lt;rule name="L2TP login to routers"&gt;
         &lt;match repeatCount="0" repeatInterval="60"&gt;^l2tp,ppp,info,account (.*) logged in, (.*)&lt;/match&gt;
         &lt;event params="2"&gt;100811&lt;/event&gt;
         &lt;severity&gt;5&lt;/severity&gt;
         &lt;tag&gt;l2tp&lt;/tag&gt;
         &lt;description&gt;Trigger a login event when VPN logins to routers occur&lt;/description&gt;
      &lt;/rule&gt;
      &lt;rule name="Synology Admin Logins"&gt;
         &lt;match repeatCount="0" repeatInterval="120"&gt;(Connection admin:.*User.*logged in from.*)&lt;/match&gt;
         &lt;event params="1"&gt;100801&lt;/event&gt;
         &lt;severity&gt;64&lt;/severity&gt;
         &lt;tag&gt;Connection&lt;/tag&gt;
         &lt;description&gt;Trigger Log event when synology admin logins occur&lt;/description&gt;
      &lt;/rule&gt;
      &lt;rule name="unifi current time not set"&gt;
         &lt;match repeatCount="0" repeatInterval="120"&gt;(.*current time is not set yet)&lt;/match&gt;
         &lt;event params="1"&gt;100813&lt;/event&gt;
         &lt;severity&gt;5&lt;/severity&gt;
         &lt;facility&gt;1&lt;/facility&gt;
         &lt;tag&gt;syswrapper&lt;/tag&gt;
         &lt;description&gt;Log event when ntp is not updating on unifi devices&lt;/description&gt;
      &lt;/rule&gt;
   &lt;/rules&gt;
   &lt;macros/&gt;
&lt;/parser&gt;
</code></pre>
<p dir="auto">syslog format:</p>
<pre><code>16.01.2018 16:20:18	r01.domain.name	1	5	r01.domain.name	l2tp	l2tp,ppp,info,account USERNAME logged in, IPADDRESS
</code></pre>
]]></description><link>https://forum.netxms.org/topic/5398/syslog-parser-rules-not-working</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 14:50:18 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5398.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 16 Jan 2018 06:31:33 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to syslog parser rules not working on Thu, 12 Jul 2018 04:53:03 GMT]]></title><description><![CDATA[<p dir="auto">Just to answer my own question, as usual the problem was PEBKAC.</p>
<p dir="auto">I had opened the syslog monitor next to the parser window during testing and conflated the severity column in the syslog window with the severity tag in the parser window. </p>
<p dir="auto">A debug log reveled the match was missing on the severity and I realised the parser severity is a bit mask and not representative of the syslog window.  So a semantic difference with the same name.</p>
<p dir="auto">Correcting that has the rules working now.</p>
<p dir="auto">Cheers.</p>
]]></description><link>https://forum.netxms.org/post/24512</link><guid isPermaLink="true">https://forum.netxms.org/post/24512</guid><dc:creator><![CDATA[normalcy]]></dc:creator><pubDate>Thu, 12 Jul 2018 04:53:03 GMT</pubDate></item></channel></rss>