Scheduling archiving

Team,
Is there a way to do a weekly archive schedule?
This is to prevent the error message about the log being full.
Thank you - Will
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content

Dear @ITV
ITV wrote
Team,
Is there a way to do a weekly archive schedule?
This is to prevent the error message about the log being full.
Thank you - Will
Omada SDN Controller will automatically delete the oldest 10% of logs. Therefore, you may not worry about that.
But if you get such alerts frequently, there are probably a lot of client roaming events, which generate many logs. You can go to Log – Notifications, to adjust the notification settings. For example, you can uncheck “Log full” notification in System, or “Client Roaming (Wireless)” notification in Client, or other frequent log types.
See more details:
What to do if you get an alert of “The number of logs is up to the limit”
- Copy Link
- Report Inappropriate Content
Yes we get these messages frequently - at least once a week.
I already disabled the fast-roaming stuff to reduce the roaming attempts.
Which brings it back to once a month.
Disabling messages is not really an option for governance/security reasons:
These messages are forwarded to Splunk for risc analysis on the network usage and the behavior of the clients.
Hence we really need these!
Any other suggestions?
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 558
Replies: 2
Voters 0
No one has voted for it yet.