<?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 parsing for unknown nodes possible?]]></title><description><![CDATA[<p dir="auto">I noticed NetXMS will not parse syslog messages unless it can map the source IP address to a known node that is being monitored. Is there a way to change this behavior?<br />
I have some scripts that send syslog error messages on customer routers and I want to get alerts for them. Currently not possible unless I add the node into NetXMS which I don't want to do</p>
<p dir="auto">Also i've had some issues with this whereby the source address of a device is i.e. 1.2.3.4 but NetXMS is using 5.6.7.8 and it won't parse the syslog message as it thinks it doesn't belong to that node</p>
<p dir="auto">I understand for syslog storing it has to know which node to put the messages under. But I mostly only care about realtime alerts so I don't care if the syslog messages gets immediately dropped afterwards, but I want the parser to work on them so I can push a notification to SLACK</p>
]]></description><link>https://forum.netxms.org/topic/6352/syslog-parsing-for-unknown-nodes-possible</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 17:13:48 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6352.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 18 Dec 2019 05:13:06 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to SysLog parsing for unknown nodes possible? on Wed, 18 Dec 2019 13:47:14 GMT]]></title><description><![CDATA[<p dir="auto">No, it is not possible without server source code changes.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/27173</link><guid isPermaLink="true">https://forum.netxms.org/post/27173</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 18 Dec 2019 13:47:14 GMT</pubDate></item></channel></rss>