This is more of a is this ok kind of question
I need to enable debug level syslog for a particular AP and send it out to a syslog server until we can reproduce an issue.
Now I know it is not best practice to leave debug level logs on all the time on the controller, etc.. but what problems may I run into if I do this...
I may have to keep this going for example like 2 weeks...
in my experience, syslog debug level can be a bit excessive, and the majority of the messages are not terribly
helpful in daily monitoring.
i'd stick to WARN or INFO level for daily use.
It is good practice to have syslog servers configured on all network devices, and be prepared to enable
appropriate and useful levels of syslog messages for troubleshooting purposes.
And as always, SNMP traps and any level of syslog messages correlated at a central server are an excellent source
of chronological event information covering the entire network.
Thanks for the feedback on this.
I will leave it as is for now as the logs are being analyzed by someone else. I'd rather give them everything and they can filter out what they do not need.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.