syslog to remote server, issue with identifier

User avatar
DTaftJr
Member
 
Posts: 4
Joined: Thu Jul 23, 2015 5:54 pm
Has thanked: 2 times
Been thanked: 0 time

syslog to remote server, issue with identifier

Fri May 25, 2018 8:18 pm

Read through a few pages after searching the forum for "syslog" and didn't see anything pertaining to this.

The switch syslog implementation does not appear to be setting the identifier or ID field.

In any situation where our syslog server is separated by a NAT'd network all switches behind that NAT'd IP just show up as the same IP address leaving us with no way of telling which switch sent the message aside from logging into every single one and checking the logs on the device to find it.

As stated pretty much every other syslog implementation uses the hostname field as the identifier if this could be implemented it would save A LOT of time when syslog alerts pop that need attention.

On a secondary note it would be nice to have the ability to set a log-prefix as well. Heck this alone would be fine as even if the above wasn't available I could just set an ID in the prefix field.

User avatar
Stephen
Employee
Employee
 
Posts: 1033
Joined: Sun Dec 24, 2017 8:56 pm
Has thanked: 85 times
Been thanked: 181 times

Re: syslog to remote server, issue with identifier

Sat Jun 02, 2018 4:49 pm

Hello Dtaftjr

This feature has been added to the next coming release.

Return to General Discussion

Who is online

Users browsing this forum: No registered users and 50 guests