Syslog values randomly changing

[Stephen_Stormon]

We have a number of switches connected to Extreme Management Center (all with the same syslog settings configured).  One of the switches has twice now changed the syslog settings which apparently was caused by the “Syslog Refresh” setting in XMC.

I don’t fully understand why the change was made on the one switch and not others, but the suggestion was to turn off that “syslog refresh” feature.  What I’m trying to figure out is what the difference is between the two statements:

The fist time it happened:

Old: configure log target syslog 1.2.3.4:514 vr VR-Default local0 format timestamp seconds date Mmm-dd event-name none process-slot priority host-name tag-name

New: configure log target syslog 1.2.3.4:514 vr VR-Default local0 format timestamp seconds date Mmm-dd event-name condition priority host-name tag-name

The second time it happened it went from:

event-name none process slot priority tag-name

to:

event-name condition priority host-name tag name

Should we change the statement on all of our switches to “event-name condition priority host-name tag name”?

[Stefan_K_ · Accepted solution]

As far as I understand from the CLI and the Command reference…

event-name none = doesn’t display the name of the component in the log entry.

event-name component = displays the name of the component 
event-name condition = displays the name of the component incl. condition

process-name = includes the internal name of the process

More information can be found in the command reference on page 778: ExtremeXOS® Command Reference Guide - for Version 30.7 (extremenetworks.com)
Per EXOS Default it is set to event-name none.