NimbostratusRequest Log can get cycled through if you are having a high rate of traffic, or it's been a long time since the correlation event was logged, or the related events might have been cleared (deleted) manually. Local logging is also not guaranteed by default and could fall through if the system is otherwise busy, but this rarely happens unless on very busy boxes.
By default, at about 2GB of disk usage, older events will start to be deleted, and also at 3 million records, whichever one is reached first. These limits can take ages on a device in the lab, but easily take half a day on a busy production site. Local logging is meant for quick troubleshooting only and for anything more extensive, you should have off-box logging (many logging destinations are supported).
It might help to go through the manual as well: https://support.f5.com/kb/en-us/products/big-ip_asm/manuals/product/asm-config-11-2-0/asm_monitoring.html?sr=528965261055514
CirrostratusHello BinaryCanary,
Is it possible to change/reduce these values ? If yes how because I didn't find any doc. about it (ASM v12.1.2)
For example, to pass the ASM log DB size from 2GB to 1GB and the 3 Million to 1.5 Million ?
Thanks
