Bug #709

Monitoring Subsystem : custom metric is not forgotten when undefined

Added by jordan pittier about 10 years ago. Updated almost 10 years ago.

Status:ClosedStart date:07/07/2011
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Resolution: Pull request:
Affected Versions:

Description

Hi,
I have setup a small script in var/remotes/im/kvm.d/mycustommetric following this http://www.opennebula.org/documentation:rel2.2:img guide. My script outputs "TEMPERATURE=banana" (it's a test). "onehost sync" and "onehost show 0" work as expected. Now I want to remove this useless script (because obviously a temperature can not be equal to a banana). But "onehost show 0" (after a proper onehost sync) keeps outputting

MONITORING INFORMATION
ARCH=x86_64
[...]
TEMPERATURE=banana
[...]

Even though my custom script doesnt exist anymore. Is there a "cache" mecanism ? How can I clear it ?

And btw, var/remotes/im/common.d doesnt seem to work anymore, scripts inside are not executed.

Thanks guys ! v3 sounds awesome :)

History

#1 Updated by Ruben S. Montero almost 10 years ago

  • Status changed from New to Closed

Metrics are stored in the host template. In OpenNebula 2.2 there is no straightforward mechanisms to remove the value. However in OpenNebula 3.0 you can edit the templates to remove the metric (or to add custom metadata to use in REQUIREMENTS without the need of adding a probe).

I am closing this one as it is solved in the next release.

Thanks for your feedback!

Cheers

Also available in: Atom PDF