There's no need to emit a check metric for the http_check plugin
because it doesn't probe a single service.
Closes-Bug: #1618000
Change-Id: I1ed7f59039eaf594a7a4596f7af7f186e900c532
* Split out object/workers stats collection for Nova, Cinder and Neutron plugins
* Use the common interface exposed by collectd_base.Base
Change-Id: I59f698b8f09fd0d3ce375327d9e4d81d767d961c
Without this change, Python plugins running external processes never
get the return code. See the collectd code [1] for the details.
The patch removes the call to init_callback() when not necessary.
[1] https://github.com/collectd/collectd/blob/master/contrib/python/getsigchld.py
Co-Authored-By: Simon Pasquier <spasquier@mirantis.com>
Change-Id: I32354319ef30cea0c1514a45c419f7d15047664a
This change adds a collectd plugin that gets metrics from the Pacemaker
cluster:
- cluster's metrics
- node's metrics
- resource's metrics
Most of the metrics are only collected from the node that is the
designated controller except pacemaker_resource_local_active and
pacemaker_dc_local_active.
The plugin also removes the 'pacemaker_resource' plugin by providing the
exact same metrics and notifications for the other collectd plugins.
Finally the plugin is also installed on the standalone-rabbitmq and
standalone-database nodes if they are present.
Change-Id: I8b5b987704f69c6a60b13e8ea982f27924f488d1
The check metrics are always emitted by Python plugins to express
the success or the failure of the metric collection.
Some plugins don't emit the check metric because it is redundant for them.
This applies to all the openstack_* plugins where
check_openstack_api plugin has the same meaning than 'check' metrics.
The patch fixes also the error handling for the rabbitmq_info plugin.
Change-Id: Ic972e81ddd955e718bbc45b4b8502fa8ea3c2939
This is to avoid potential clashes with modules names as we experienced
with openstack.py.
Change-Id: I8380b419de0ce2ac3d98baa7a3c263c09508837f
Related-Bug: #1551622
Andreas Jaeger