Backlog #5372

Option to not store monitoring data to the DB

Added by Mariano Guezuraga almost 2 years ago. Updated almost 2 years ago.

Status:PendingStart date:09/18/2017
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Drivers - Monitor
Target version:Release 5.6

Description

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)

History

#1 Updated by Ruben S. Montero almost 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.

#2 Updated by Mariano Guezuraga almost 2 years ago

Thanks for clarifying.

Is there a feature or flag to disable writing VM information back to the DB? (Which is what I'm looking for)

#3 Updated by Ruben S. Montero almost 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)?

#4 Updated by Ruben S. Montero almost 2 years ago

  • Subject changed from Setting VM_INDIVIDUAL_MONITORING = 'no' does not stop VM monitoring to Option to not store monitoring data to the DB

#5 Updated by Mariano Guezuraga almost 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:

For example:

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)

#6 Updated by Mariano Guezuraga almost 2 years ago

Actually, it's not only monitoring information, these updates also store the entire VM template, which in our case tends to be a bit verbose, so we have big update statements

#7 Updated by Ruben S. Montero almost 2 years ago

  • Tracker changed from Request to Backlog
  • Target version set to Release 5.6

This issue is to add a flag to optionally disable the storage of monitoring data to DB.

Also available in: Atom PDF