For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

LoanBMT's avatar
LoanBMT
Icon for Nimbostratus rankNimbostratus
Oct 01, 2015

ASM Event log with local storage

Hi all,   May you help me the way to extend local data storage volume for ASM Event logs? I have been using default profile named "Log illegal requests" in TMOS 11.6, and I don't have remote stora...
application delivery
deployment
monitor
performance
storage
TMSH
Hannes_Rapp's avatar
Hannes_Rapp
Icon for Nimbostratus rankNimbostratus
Oct 01, 2015

You can modify the DB log-rotate value from the default of 8 days to 30, this should also cover for /var/log/asm and ASM logs in GUI. Note that there are no guarantees you will always have the backlog for 30 days. If you run out of disk space in /var/log folder, the actual number of days for which you will have the logs will be less.

Increasing log-age value

tmsh modify sys db logrotate.logage value 30
tmsh save sys config

If you would like to increase the disk space for /var/log folder, you can also do it from TMSH; that procedure (Extending disk space for increased logging) is documented in this article: https://support.f5.com/kb/en-us/solutions/public/14000/900/sol14952.htmlproc3

LoanBMT's avatar
LoanBMT
Icon for Nimbostratus rankNimbostratus
Nov 13, 2015
Thank you Hannes Rapp! Sorry for late reply. I think, as recommended, and with my auditing plan, it's better that I should not enable "send_content_events". I'm looking for the solution with new behavior to extend asm local storage, before I implement remote logging plan. Thank you again. Loan.