Use of /var/log/monitors? Include to logrotate?

Big-ip doesn't log monitor information by default. My guess is that you have some monitors assigned that have the debug setting enabled in their properties. This is only recommended if you are actively troubleshooting after which debug should be disabled. See this article for more log mgmt info: SOL13367

Your guess was right. I don´t know why but every single host had debugging enabled.

I disabled all debugging and deleted the log files. Thank you for your help.

So....I'm having the same problem, however, I'm not sure where to find the debugging settings nor how to clear up the disk space. Can I get some insight?

Thank you

Hi mate,

To enable/disable debugging (where the option is available) head to: Local Traffic -> Monitors -> Monitor_Name -> set Configuration to Advanced in the drop down box, then scroll to the bottom of the page, you will see the option to enable or disable debug.

For example, have a look at the PostgresSQL monitor type.

To clear the disk up, you can do it via SSH or SCP. Choose your method and navigate to /var/log. You should be able to see the monitor logs eg. POSTGRESQL__Common_HM_some.domain.com

Thanks Ryan! I'll give it a try and let you know how it turns out. Thanks for your help!

I looked through my monitors and cannot find one that has debug enabled. I also looked in the /var/log folder and there a lot of disk latency and disk statistics logs. Any ideas? The example logs are below.

disk_statistics.log.1.gz through disk_statistics.log.25.gz

and

disk_latency.log.1.gz through disk_latency.log.25.gz

I also see a lot of messages.gz and ltm.gz

Also, is there a way to list all of the monitors and their configs through the cli? I am running the virtual edition 11.5.1.

you can list all your monitors with:

tmsh list ltm monitor

So here's what I found, in the /var/log/monitors directory, there was a file that had taken up all the space. It appeared to be a monitor for one of my nodes, I may have inadvertently enabled http monitoring on one of the backend nodes by mistake.

Anyway, Thank you all for your help!