Option to not store monitoring data to the DB
|Category:||Drivers - Monitor|
|Target version:||Release 5.6|
After setting VM_INDIVIDUAL_MONITORING = 'no' and 'VM_MONITORING_EXPIRATION_TIME' = 0 I can see in the database queries updating history, like: 'REPLACE INTO history <stuff>' or 'REPLACE INTO vm_pool <stuff>'.
This is also visible when running DEBUG=3, doing:
"sudo systemctl status opennebula" shows:
[Z100][VMM][D]: VM XXX successfully monitored: STATE=a CPU=13.08 MEMORY=16777216 NETRX=31621747954 NETTX=6476584120
However, Sunstone doesn't display anymore individual VM stats (which is expected)
#1 Updated by Ruben S. Montero over 2 years ago
- Status changed from Pending to Closed
- Resolution set to worksforme
This is for disabling OpenNebula polling each VM individually. The default behavior is to gather monitor data from the host information. This is not disable with this command but removing the probe from the monitor probe directory.
#3 Updated by Ruben S. Montero over 2 years ago
- Tracker changed from Bug to Request
- Status changed from Closed to Pending
Not out of the box. You can however modify the poll probe to only send the VM state information. I'm moving this to request to evaluate this feature for a future version. Could you elaborate a bit about your use case (i.e. no wanting to write monitor data in the database)?
#5 Updated by Mariano Guezuraga over 2 years ago
We have other ways to monitor VMs (sending metrics to graphite, for example). Right now we have ~1400 VMs running and these probes are generating a lot of data in MySQL binlogs as 'REPLACE INTO vm_pool' / 'REPLACE INTO history' queries:
mguezuraga@ourdatabase$ sudo mysqlbinlog -vvv binlog.023501 | grep UPDATE | sort | uniq -c
4 ### UPDATE `opennebula`.`datastore_pool`
5448 ### UPDATE `opennebula`.`history`
1293 ### UPDATE `opennebula`.`host_pool`
5451 ### UPDATE `opennebula`.`vm_pool`
(binlog files are rotated every minute)