From 136d3669026fc558fd652f0820a86ee165fce334 Mon Sep 17 00:00:00 2001 From: Ruben Kerkhof Date: Tue, 18 Dec 2018 18:52:08 +0100 Subject: [PATCH] collectd.conf(5): fix a few typos --- src/collectd.conf.pod | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod index 1251d245..fe5291c8 100644 --- a/src/collectd.conf.pod +++ b/src/collectd.conf.pod @@ -9427,23 +9427,23 @@ dispatched. 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. +This option is only useful when 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, +The reader instance will only query the domains with attached matching tag. +Tags should have the form of 'virt-X' where X is the 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. +ever be 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. +Domain tagging is done with a custom attribute in the libvirt domain metadata +section. Value is selected by an XPath I +expression in the I namespace. (XPath and namespace values are not configurable yet). -Tagging could be used by management application to evenly spread the +Tagging could be used by management applications 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. -- 2.11.0