X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=src%2Fcollectd.conf.pod;h=69e5005635c24998001eeab65f8e6016b9c27857;hb=6725a91fd6be18b6f3475fc0eeccfb6424a73f5c;hp=e85ac1d4666ee79f5f169c51ba5245839086a170;hpb=a49486bffc401f74009037b49fb7feb420c92452;p=collectd.git diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod index e85ac1d4..69e50056 100644 --- a/src/collectd.conf.pod +++ b/src/collectd.conf.pod @@ -1,3 +1,5 @@ +=encoding UTF-8 + =head1 NAME collectd.conf - Configuration for the system statistics collection daemon B @@ -109,7 +111,7 @@ interval, that setting will take precedence. =back -=item B I [I] +=item B I If I points to a file, includes that file. If I points to a directory, recursively includes all files within that directory and its @@ -119,15 +121,29 @@ use statements like the following: Include "/etc/collectd.d/*.conf" +Starting with version 5.3, this may also be a block in which further options +affecting the behavior of B may be specified. The following option is +currently allowed: + + + Filter "*.conf" + + +=over 4 + +=item B I + If the C function is available on your system, a shell-like wildcard I may be specified to filter which files to include. This may be used in combination with recursively including a directory to easily be able to arbitrarily mix configuration files and other documents (e.g. README files). -The following statement is similar to the example above but includes all files +The given example is similar to the first example above but includes all files matching C<*.conf> in any subdirectory of C: Include "/etc/collectd.d" "*.conf" +=back + If more than one files are included by a single B option, the files will be included in lexicographical order (as defined by the C function). Thus, you can e.Eg. use numbered prefixes to specify the @@ -419,6 +435,8 @@ possibly filtering or messages. # StoreRates false # GraphitePrefix "collectd." # GraphiteEscapeChar "_" + # GraphiteSeparateInstances false + # GraphiteAlwaysAppendDS false # Receive values from an AMQP broker @@ -556,6 +574,19 @@ In I metric name, dots are used as separators between different metric parts (host, plugin, type). Default is "_" (I). +=item B B|B + +If set to B, the plugin instance and type instance will be in their own +path component, for example C. If set to B (the +default), the plugin and plugin instance (and likewise the type and type +instance) are put into one component, for example C. + +=item B B|B + +If set to B, append the name of the I (DS) to the "metric" +identifier. If set to B (the default), this is only done when there is +more than one DS. + =back =head2 Plugin C @@ -1092,16 +1123,34 @@ host name setting. Use I as the plugin instance when submitting values. Defaults to an empty string (no plugin instance). +=item B I I + +If an XPath expression references namespaces, they must be specified +with this option. I is the "namespace prefix" used in the XML document. +I is the "namespace name", an URI reference uniquely identifying the +namespace. The option can be repeated to register multiple namespaces. + +Examples: + + Namespace "s" "http://schemas.xmlsoap.org/soap/envelope/" + Namespace "m" "http://www.w3.org/1998/Math/MathML" + =item B I + =item B I + =item B B|B + =item B B|B + =item B I + =item B
I
+ =item B I These options behave exactly equivalent to the appropriate options of the -I plugin. Please see there for a detailed description. +I. Please see there for a detailed description. =item EB IE @@ -5138,6 +5187,97 @@ This optional setting sets the type instance to use. =back +=head2 Plugin C + +The I reads files in the CSV format, e.g. the statistics file +written by I. + +B + + + + Type "percent" + Instance "dropped" + Index 1 + + + Instance "snort-eth0" + Interval 600 + Collect "snort-dropped" + + + +The configuration consists of one or more B blocks that define an index +into the line of the CSV file and how this value is mapped to I +internal representation. These are followed by one or more B blocks +which configure which file to read, in which interval and which metrics to +extract. + +=over 4 + +=item EB IE + +The B block configures a new metric to be extracted from the statistics +file and how it is mapped on I data model. The string I is +only used inside the B blocks to refer to this block, so you can use +one B block for multiple CSV files. + +=over 4 + +=item B I + +Configures which I to use when dispatching this metric. Types are defined +in the L file, see the appropriate manual page for more +information on specifying types. Only types with a single I are +supported by the I. The information whether the value is an +absolute value (i.e. a C) or a rate (i.e. a C) is taken from the +I definition. + +=item B I + +If set, I is used to populate the type instance field of the +created value lists. Otherwise, no type instance is used. + +=item B I + +Configure to read the value from the field with the zero-based index I. +If the value is parsed as signed integer, unsigned integer or double depends on +the B setting, see above. + +=back + +=item EB IE + +Each B block represents one CSV file to read. There must be at least one +I block but there can be multiple if you have multiple CSV files. + +=over 4 + +=item B I + +Sets the I used when dispatching the values. + +=item B I + +Specifies which I to collect. This option must be specified at least +once, and you can use this option multiple times to specify more than one +metric to be extracted from this statistic file. + +=item B I + +Configures the interval in which to read values from this instance / file. +Defaults to the plugin's default interval. + +=item B I + +Rather than using the local time when dispatching a value, read the timestamp +from the field with the zero-based index I. The value is interpreted as +seconds since epoch. The value is parsed as a double and may be factional. + +=back + +=back + =head2 Plugin C The C connects to the query port of a teamspeak2 server and @@ -5366,7 +5506,33 @@ Take the UUID from the given file (default I). =head2 Plugin C -The Varnish plugin collects information about Varnish, an HTTP accelerator. +The I collects information about Varnish, an HTTP accelerator. + +Synopsis: + + + + CollectCache true + CollectConnections true + CollectBackend true + CollectSHM true + CollectESI false + CollectFetch false + CollectHCB false + CollectSMA false + CollectSMS false + CollectSM false + CollectTotals false + CollectWorkers false + + + +The configuration consists of one or more EBEIE +blocks. I is the parameter passed to "varnishd -n". If left empty, it +will collectd statistics from the default "varnishd" instance (this should work +fine in most cases). + +Inside each EBE blocks, the following options are recognized: =over 4 @@ -5523,7 +5689,7 @@ instance) are put into one component, for example C. =item B B|B -If set the B, append the name of the I (DS) to the "metric" +If set to B, append the name of the I (DS) to the "metric" identifier. If set to B (the default), this is only done when there is more than one DS. @@ -5570,6 +5736,16 @@ If set to B (the default), convert counter values to rates. If set to B counter values are stored as is, i.e. as an increasing integer number. +=item B I + +=item B I + +=item B I + +Sets the information used when authenticating to a I database. The +fields are optional (in which case no authentication is attempted), but if you +want to use authentication all three fields must be set. + =back =head2 Plugin C @@ -5739,7 +5915,7 @@ When a value comes within range again or is received after it was missing, an Here is a configuration example to get you started. Read below for more information. - + WarningMin 0.00 WarningMax 1000.00 @@ -5770,7 +5946,7 @@ information. - + There are basically two types of configuration statements: The C, C, and C blocks select the value for which a threshold should be @@ -6177,19 +6353,36 @@ Available options: =item B I Name of the write plugin to which the data should be sent. This option may be -given multiple times to send the data to more than one write plugin. +given multiple times to send the data to more than one write plugin. If the +plugin supports multiple instances, the plugin's instance(s) must also be +specified. =back If no plugin is explicitly specified, the values will be sent to all available write plugins. -Example: +Single-instance plugin example: Plugin "rrdtool" +Multi-instance plugin example: + + + + ... + + + ... + + + ... + + Plugin "write_graphite/foo" + + =item B Starts processing the rules of another chain, see L<"Flow control"> above. If