Hi, there is actually a log level management that you can tune in /etc/{default,sysconfig}/centreon_vmware by setting --severity=error and then systemctl restart centreon_vmware.

Can you paste here a sample of the log messages that fill your log files?

hello

indeed there is that file in sysconfig, with “--severity=info”, I’ve changed it to error, kept a copy of the log file already 400MB and restarted, the file is not growing anymore.

in the log file there were these kind of messages, multiple per seconds sometimes (I’m monitoring quite lot of datastore and a few dozen hosts), this is a single line of log

p2025-01-16 10:56:10] 1info] vpshere 'XXXX' handler asking: {"connector_hostname":"localhost","connector_port":"5700","warning-write-latency":"","vsphere_password":null,"warning-status":"","filter":null,"sampling_period":null,"identity":"client-0b8f356a9f4e46438ff0c6503e9dXXX","container":"XXXX","list_counters":null,"critical-status":"","filter_datastore":"","unknown-write-latency":null,"display_ok_counters":null,"unknown_connector_status":null,"vsphere_username":null,"command":"datastorehost","warning_connector_status":null,"unknown-status":"$values->{status} !~ /^connected$/i","scope_datacenter":null,"esx_hostname":"xxxxxxxxxxxxxxx","datastore_name":"XXXXX-1","unknown-read-latency":null,"scope_cluster":null,"critical_connector_status":null,"time_shift":0,"filter_counters_block":null,"critical-read-latency":"","vsphere_address":null,"filter_counters":null,"warning-read-latency":"","critical-write-latency":"","timeout":null,"case_insensitive":null}