Forum Discussion
ASM syslogs vs blocked request logs?
- Jan 27, 2016
send_content_events is only concerning logging to
on the device./var/log/asm
ASM event logs in the GUI should continue to work as configured in the logging profile if you have specified.
ASM local event log files are cycled after 3,000,000 records, or 2GB of disk usage, so this could explain why you don't see some support IDs in the database, particularly if a long time has passed since the support ID was generated.
For this reason, it is often advisable to use a remote logging server to store logs more extensively (it also helps to reduce load on the ASM).
send_content_events is only concerning logging to
/var/log/asm
on the device.
ASM event logs in the GUI should continue to work as configured in the logging profile if you have specified.
ASM local event log files are cycled after 3,000,000 records, or 2GB of disk usage, so this could explain why you don't see some support IDs in the database, particularly if a long time has passed since the support ID was generated.
For this reason, it is often advisable to use a remote logging server to store logs more extensively (it also helps to reduce load on the ASM).
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com