The LTM is going to send anything and everything it has to the Remote Syslog Server. As long at you are seeing the same log entries on the source device then you probably already have it setup correctly (it’s a pretty straight forward process).
Keep in mind that if you continue to edit the logging level that you may miss something that you actually want to see just for the sake of not overloading your remove syslog server.
The LTM is going to send anything and everything it has to the Remote Syslog Server. As long at you are seeing the same log entries on the source device then you probably already have it setup correctly (it’s a pretty straight forward process).
Keep in mind that if you continue to edit the logging level that you may miss something that you actually want to see just for the sake of not overloading your remove syslog server.
But all those are informational logs. almost 4 logs per second and LTM is not even in production yet, its only configured. There has to be a way to lower the severity of logs for remote server
But all those are informational logs. almost 4 logs per second and LTM is not even in production yet, its only configured. There has to be a way to lower the severity of logs for remote server
I deal with the repetitive syslog messages in the Kiwi syslog server. Create a rule that filters based on the IPs of the f5 devices AND unique text strings of the repetitive messages (you can stack up filters and actions in Kiwi), with an action that stops message processing. Example:
filter = Message text “POST iControl/iControlPortal.cgi” OR “pam_unix(crond:session)”
filter = Hostname “10.150.0.10” OR “10.150.0.11” OR “10.150.0.12” OR “10.150.0.13” OR “10.150.0.14”
action = Stop message processing
Place this rule near the top of the list (order matters in Kiwi). It will drop the useless stuff, and allow the meaningful messages to pass through to be parsed, logged/emailed/whatever. Hope this helps.