From: Pavel Rochnyack Date: Sun, 2 Dec 2018 18:24:36 +0000 (+0700) Subject: virt: Merge changes from master to resolve conflict X-Git-Url: https://git.octo.it/?p=collectd.git;a=commitdiff_plain;h=5d1fc8f895b30d6a4f868e560c68dbf4f5bd03c3;hp=d3eae6bf3df995566cad90c96a1dea49652b5dd2 virt: Merge changes from master to resolve conflict --- diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod index 8960597d..ae52beea 100644 --- a/src/collectd.conf.pod +++ b/src/collectd.conf.pod @@ -9402,11 +9402,38 @@ B: I metrics can't be collected if I plugin is enabled. =back =item B B|B + Override default configuration to only send notifications when there is a change in the lifecycle state of a domain. When set to true notifications will be sent for every read cycle. Default is false. Does not affect the stats being dispatched. +=item B B + +How many read instances you want to use for this plugin. The default is one, +and the sensible setting is a multiple of the B value. + +This option is only useful then domains are specially tagged. +If you are not sure, just use the default setting. + +The reader instance will only query the domains with attached a matching tag. +Tags should have the form of 'virt-X' where X is reader instance number, +starting from 0. + +The special-purpose reader instance #0, guaranteed to be always present, +will query all the domains with missing or unrecognized tag, so no domain will +ever left out. + +Domain tagging is done with custom attribute in the libvirt domain metadata +section. Value is taken by XPath I +expression in I namespace. +(XPath and namespace values are not configurable yet). + +Tagging could be used by management application to evenly spread the +load among the reader threads, or to pin on the same threads all +the libvirt domains which use the same shared storage, to minimize +the disruption in presence of storage outages. + =back =head2 Plugin C