NetXMS agent as syslog proxy/forwarder?

[tomaskir]

Yes, syslog proxy has been fully implemented, zone matching is properly supported, etc.

We use Raspbian Lite on our Pis.

[jdowney]

Thanks,

EnableSyslogProxy = yes

Anything wrong with this using - NetXMS agent 2.1-M2 (windows) Please see attached.

---

[tomaskir]

All proxy related settings are this:

# Proxying related settings
EnableProxy = yes
EnableSNMPProxy = yes
EnableSNMPTrapProxy = yes
EnableSyslogProxy = yes
ZoneId = 1017

You need to configure ZoneId for proper zone matching of Syslog and SNMP Traps.

[jdowney]

Thanks Tomaskir working now!

 ;D

[jdowney]

Should all agents in each zone have the Zone ID specified? Or just the machines that are being used as proxies?

Also am I correctly in thinking the proxy's cache Syslog and SNMP traps etc when a link to the master server is lost?

John

[tomaskir]

@jdowney said in NetXMS agent as syslog proxy/forwarder?:

Should all agents in each zone have the Zone ID specified? Or just the machines that are being used as proxies?

Also am I correctly in thinking the proxy's cache Syslog and SNMP traps etc when a link to the master server is lost?

John

Only the proxy needs ZoneId configured.

I am actually not sure about caching - Viktor will be the best to answer that.

[victor]

Hi,

yes, agent will cache syslog records and SNMP traps, but only in memory. If you restart agent while there is no connection, unsent records will be lost.

Best regards,
Victor

[jdowney]

Thanks, Victor that's helpful info.

[AleCoelli]

Hi Victor, this it a quite old post, but I think that agent still cache syslog records and SNMP traps only in memory.
Do you think that it will be possible to cache to disk some data  instead of memory? when we have long power outage on our customer site, we lost a lot of information about what's appened during the outage..

thanks
Alessandro

[victor]

Hi,

latest agent versions do store syslog records and SNMP traps in local database (since version 3.4).

Best regards,
Victor