3 collectd.conf - Configuration for the system statistics collection daemon B<collectd>
7 BaseDir "/path/to/data/"
8 PIDFile "/path/to/pidfile/collectd.pid"
9 Server "123.123.123.123" 12345
22 This config file controls how the system statistics collection daemon
23 B<collectd> behaves. The most significant option is B<LoadPlugin>, which
24 controls which plugins to load. These plugins ultimately define collectd's
27 The syntax of this config file is similar to the config file of the famous
28 B<Apache Webserver>. Each line contains either a key-value-pair or a
29 section-start or -end. Empty lines and everything after the hash-symbol `#' is
30 ignored. Values are either string, enclosed in double-quotes,
31 (floating-point-)numbers or a boolean expression, i.E<nbsp>e. either B<true> or
32 B<false>. String containing of only alphanumeric characters and underscores do
33 not need to be quoted. Lines may be wrapped by using `\' as the last character
34 before the newline. This allows long lines to be split into multiple lines.
35 Quoted strings may be wrapped as well. However, those are treated special in
36 that whitespace at the beginning of the following lines will be ignored, which
37 allows for nicely indenting the wrapped lines.
39 The configuration is read and processed in order, i.E<nbsp>e. from top to
40 bottom. So the plugins are loaded in the order listed in this config file. It
41 is a good idea to load any logging plugins first in order to catch messages
42 from plugins during configuration. Also, the C<LoadPlugin> option B<must> occur
43 B<before> the C<E<lt>Plugin ...E<gt>> block.
49 =item B<BaseDir> I<Directory>
51 Sets the base directory. This is the directory beneath all RRD-files are
52 created. Possibly more subdirectories are created. This is also the working
53 directory for the daemon.
55 =item B<LoadPlugin> I<Plugin>
57 Loads the plugin I<Plugin>. There must be at least one such line or B<collectd>
58 will be mostly useless.
60 =item B<Include> I<Path>
62 If I<Path> points to a file, includes that file. If I<Path> points to a
63 directory, recursively includes all files within that directory and its
64 subdirectories. If the C<wordexp> function is available on your system,
65 shell-like wildcards are expanded before files are included. This means you can
66 use statements like the following:
68 Include "/etc/collectd.d/*.conf"
70 If more than one files are included by a single B<Include> option, the files
71 will be included in lexicographical order (as defined by the C<strcmp>
72 function). Thus, you can e.E<nbsp>g. use numbered prefixes to specify the
73 order in which the files are loaded.
75 To prevent loops and shooting yourself in the foot in interesting ways the
76 nesting is limited to a depth of 8E<nbsp>levels, which should be sufficient for
77 most uses. Since symlinks are followed it is still possible to crash the daemon
78 by looping symlinks. In our opinion significant stupidity should result in an
79 appropriate amount of pain.
81 It is no problem to have a block like C<E<lt>Plugin fooE<gt>> in more than one
82 file, but you cannot include files from within blocks.
84 =item B<PIDFile> I<File>
86 Sets where to write the PID file to. This file is overwritten when it exists
87 and deleted when the program is stopped. Some init-scripts might override this
88 setting using the B<-P> command-line option.
90 =item B<PluginDir> I<Directory>
92 Path to the plugins (shared objects) of collectd.
94 =item B<TypesDB> I<File> [I<File> ...]
96 Set one or more files that contain the data-set descriptions. See
97 L<types.db(5)> for a description of the format of this file.
99 =item B<Interval> I<Seconds>
101 Configures the interval in which to query the read plugins. Obviously smaller
102 values lead to a higher system load produced by collectd, while higher values
103 lead to more coarse statistics.
105 =item B<ReadThreads> I<Num>
107 Number of threads to start for reading plugins. The default value is B<5>, but
108 you may want to increase this if you have more than five plugins that take a
109 long time to read. Mostly those are plugin that do network-IO. Setting this to
110 a value higher than the number of plugins you've loaded is totally useless.
112 =item B<Hostname> I<Name>
114 Sets the hostname that identifies a host. If you omit this setting, the
115 hostname will be determinded using the L<gethostname(2)> system call.
117 =item B<FQDNLookup> B<true|false>
119 If B<Hostname> is determined automatically this setting controls whether or not
120 the daemon should try to figure out the "fully qualified domain name", FQDN.
121 This is done using a lookup of the name returned by C<gethostname>.
123 Using this feature (i.E<nbsp>e. setting this option to B<true>) is recommended.
124 However, to preserve backwards compatibility the default is set to B<false>.
125 The sample config file that is installed with C<makeE<nbsp>install> includes a
126 line which sets this option, though, so that default installations will have
127 this setting enabled.
129 =item B<PreCacheChain> I<ChainName>
131 =item B<PostCacheChain> I<ChainName>
133 Configure the name of the "pre-cache chain" and the "post-cache chain". Please
134 see L<FILTER CONFIGURATION> below on information on chains and how these
135 setting change the daemon's behavior.
139 =head1 PLUGIN OPTIONS
141 Some plugins may register own options. These options must be enclosed in a
142 C<Plugin>-Section. Which options exist depends on the plugin used. Some plugins
143 require external configuration, too. The C<apache plugin>, for example,
144 required C<mod_status> to be configured in the webserver you're going to
145 collect data from. These plugins are listed below as well, even if they don't
146 require any configuration within collectd's configfile.
148 A list of all plugins and a short summary for each plugin can be found in the
149 F<README> file shipped with the sourcecode and hopefully binary packets as
152 =head2 Plugin C<apache>
154 To configure the C<apache>-plugin you first need to configure the Apache
155 webserver correctly. The Apache-plugin C<mod_status> needs to be loaded and
156 working and the C<ExtendedStatus> directive needs to be B<enabled>. You can use
157 the following snipped to base your Apache config upon:
160 <IfModule mod_status.c>
161 <Location /mod_status>
162 SetHandler server-status
166 Since its C<mod_status> module is very similar to Apache's, B<lighttpd> is
167 also supported. It introduces a new field, called C<BusyServers>, to count the
168 number of currently connected clients. This field is also supported.
170 The following options are accepted by the C<apache>-plugin:
174 =item B<URL> I<http://host/mod_status?auto>
176 Sets the URL of the C<mod_status> output. This needs to be the output generated
177 by C<ExtendedStatus on> and it needs to be the machine readable output
178 generated by appending the C<?auto> argument.
180 =item B<User> I<Username>
182 Optional user name needed for authentication.
184 =item B<Password> I<Password>
186 Optional password needed for authentication.
188 =item B<VerifyPeer> B<true|false>
190 Enable or disable peer SSL certificate verification. See
191 L<http://curl.haxx.se/docs/sslcerts.html> for details. Enabled by default.
193 =item B<VerifyHost> B<true|false>
195 Enable or disable peer host name verification. If enabled, the plugin checks
196 if the C<Common Name> or a C<Subject Alternate Name> field of the SSL
197 certificate matches the host name provided by the B<URL> option. If this
198 identity check fails, the connection is aborted. Obviously, only works when
199 connecting to a SSL enabled server. Enabled by default.
201 =item B<CACert> I<File>
203 File that holds one or more SSL certificates. If you want to use HTTPS you will
204 possibly need this option. What CA certificates come bundled with C<libcurl>
205 and are checked by default depends on the distribution you use.
209 =head2 Plugin C<apcups>
213 =item B<Host> I<Hostname>
215 Hostname of the host running B<apcupsd>. Defaults to B<localhost>. Please note
216 that IPv6 support has been disabled unless someone can confirm or decline that
217 B<apcupsd> can handle it.
219 =item B<Port> I<Port>
221 TCP-Port to connect to. Defaults to B<3551>.
225 =head2 Plugin C<ascent>
227 This plugin collects information about an Ascent server, a free server for the
228 "World of Warcraft" game. This plugin gathers the information by fetching the
229 XML status page using C<libcurl> and parses it using C<libxml2>.
231 The configuration options are the same as for the C<apache> plugin above:
235 =item B<URL> I<http://localhost/ascent/status/>
237 Sets the URL of the XML status output.
239 =item B<User> I<Username>
241 Optional user name needed for authentication.
243 =item B<Password> I<Password>
245 Optional password needed for authentication.
247 =item B<VerifyPeer> B<true|false>
249 Enable or disable peer SSL certificate verification. See
250 L<http://curl.haxx.se/docs/sslcerts.html> for details. Enabled by default.
252 =item B<VerifyHost> B<true|false>
254 Enable or disable peer host name verification. If enabled, the plugin checks
255 if the C<Common Name> or a C<Subject Alternate Name> field of the SSL
256 certificate matches the host name provided by the B<URL> option. If this
257 identity check fails, the connection is aborted. Obviously, only works when
258 connecting to a SSL enabled server. Enabled by default.
260 =item B<CACert> I<File>
262 File that holds one or more SSL certificates. If you want to use HTTPS you will
263 possibly need this option. What CA certificates come bundled with C<libcurl>
264 and are checked by default depends on the distribution you use.
268 =head2 Plugin C<bind>
270 Starting with BIND 9.5.0, the most widely used DNS server software provides
271 extensive statistics about queries, responses and lots of other information.
272 The bind plugin retrieves this information that's encoded in XML and provided
273 via HTTP and submits the values to collectd.
275 To use this plugin, you first need to tell BIND to make this information
276 available. This is done with the C<statistics-channels> configuration option:
278 statistics-channels {
279 inet localhost port 8053;
282 The configuration follows the grouping that can be seen when looking at the
283 data with an XSLT compatible viewer, such as a modern web browser. It's
284 probably a good idea to make yourself familiar with the provided values, so you
285 can understand what the collected statistics actually mean.
290 URL "http://localhost:8053/"
304 Zone "127.in-addr.arpa/IN"
308 The bind plugin accepts the following configuration options:
314 URL from which to retrieve the XML data. If not specified,
315 C<http://localhost:8053/> will be used.
317 =item B<OpCodes> I<true>|I<false>
319 When enabled, statistics about the I<"OpCodes">, for example the number of
320 C<QUERY> packets, are collected.
324 =item B<QTypes> I<true>|I<false>
326 When enabled, the number of I<incoming> queries by query types (for example
327 C<A>, C<MX>, C<AAAA>) is collected.
331 =item B<ServerStats> I<true>|I<false>
333 Collect global server statistics, such as requests received over IPv4 and IPv6,
334 successful queries, and failed updates.
338 =item B<ZoneMaintStats> I<true>|I<false>
340 Collect zone maintenance statistics, mostly information about notifications
341 (zone updates) and zone transfers.
345 =item B<ResolverStats> I<true>|I<false>
347 Collect resolver statistics, i.E<nbsp>e. statistics about outgoing requests
348 (e.E<nbsp>g. queries over IPv4, lame servers). Since the global resolver
349 counters apparently were removed in BIND 9.5.1 and 9.6.0, this is disabled by
350 default. Use the B<ResolverStats> option within a B<View "_default"> block
351 instead for the same functionality.
357 Collect global memory statistics.
361 =item B<View> I<Name>
363 Collect statistics about a specific I<"view">. BIND can behave different,
364 mostly depending on the source IP-address of the request. These different
365 configurations are called "views". If you don't use this feature, you most
366 likely are only interested in the C<_default> view.
368 Within a E<lt>B<View>E<nbsp>I<name>E<gt> block, you can specify which
369 information you want to collect about a view. If no B<View> block is
370 configured, no detailed view statistics will be collected.
374 =item B<QTypes> I<true>|I<false>
376 If enabled, the number of I<outgoing> queries by query type (e.E<nbsp>g. C<A>,
381 =item B<ResolverStats> I<true>|I<false>
383 Collect resolver statistics, i.E<nbsp>e. statistics about outgoing requests
384 (e.E<nbsp>g. queries over IPv4, lame servers).
388 =item B<CacheRRSets> I<true>|I<false>
390 If enabled, the number of entries (I<"RR sets">) in the view's cache by query
391 type is collected. Negative entries (queries which resulted in an error, for
392 example names that do not exist) are reported with a leading exclamation mark,
397 =item B<Zone> I<Name>
399 When given, collect detailed information about the given zone in the view. The
400 information collected if very similar to the global B<ServerStats> information
403 You can repeat this option to collect detailed information about multiple
406 By default no detailed zone information is collected.
412 =head2 Plugin C<cpufreq>
414 This plugin doesn't have any options. It reads
415 F</sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq> (for the first CPU
416 installed) to get the current CPU frequency. If this file does not exist make
417 sure B<cpufreqd> (L<http://cpufreqd.sourceforge.net/>) or a similar tool is
418 installed and an "cpu governor" (that's a kernel module) is loaded.
424 =item B<DataDir> I<Directory>
426 Set the directory to store CSV-files under. Per default CSV-files are generated
427 beneath the daemon's working directory, i.E<nbsp>e. the B<BaseDir>.
428 The special strings B<stdout> and B<stderr> can be used to write to the standard
429 output and standard error channels, respectively. This, of course, only makes
430 much sense when collectd is running in foreground- or non-daemon-mode.
432 =item B<StoreRates> B<true|false>
434 If set to B<true>, convert counter values to rates. If set to B<false> (the
435 default) counter values are stored as is, i.E<nbsp>e. as an increasing integer
440 =head2 Plugin C<curl>
442 The curl plugin uses the B<libcurl> (L<http://curl.haxx.se/>) to read web pages
443 and the match infrastructure (the same code used by the tail plugin) to use
444 regular expressions with the received data.
446 The following example will read the current value of AMD stock from google's
447 finance page and dispatch the value to collectd.
450 <Page "stock_quotes">
451 URL "http://finance.google.com/finance?q=NYSE%3AAMD"
455 Regex "<span +class=\"pr\"[^>]*> *([0-9]*\\.[0-9]+) *</span>"
456 DSType "GaugeAverage"
457 # Note: `stock_value' is not a standard type.
464 In the B<Plugin> block, there may be one or more B<Page> blocks, each defining
465 a web page and one or more "matches" to be performed on the returned data. The
466 string argument to the B<Page> block is used as plugin instance.
468 The following options are valid within B<Page> blocks:
474 URL of the web site to retrieve. Since a regular expression will be used to
475 extract information from this data, non-binary data is a big plus here ;)
477 =item B<User> I<Name>
479 Username to use if authorization is required to read the page.
481 =item B<Password> I<Password>
483 Password to use if authorization is required to read the page.
485 =item B<VerifyPeer> B<true>|B<false>
487 Enable or disable peer SSL certificate verification. See
488 L<http://curl.haxx.se/docs/sslcerts.html> for details. Enabled by default.
490 =item B<VerifyHost> B<true>|B<false>
492 Enable or disable peer host name verification. If enabled, the plugin checks if
493 the C<Common Name> or a C<Subject Alternate Name> field of the SSL certificate
494 matches the host name provided by the B<URL> option. If this identity check
495 fails, the connection is aborted. Obviously, only works when connecting to a
496 SSL enabled server. Enabled by default.
498 =item B<CACert> I<file>
500 File that holds one or more SSL certificates. If you want to use HTTPS you will
501 possibly need this option. What CA certificates come bundled with C<libcurl>
502 and are checked by default depends on the distribution you use.
504 =item B<MeasureResponseTime> B<true>|B<false>
506 Measure response time for the request. Disabled by default.
508 =item B<E<lt>MatchE<gt>>
510 One or more B<Match> blocks that define how to match information in the data
511 returned by C<libcurl>. The C<curl> plugin uses the same infrastructure that's
512 used by the C<tail> plugin, so please see the documentation of the C<tail>
513 plugin below on how matches are defined.
517 =head2 Plugin C<curl_json>
519 The B<curl_json plugin> uses B<libcurl> (L<http://curl.haxx.se/>) and
520 B<libyajl> (L<http://www.lloydforge.org/projects/yajl/>) to retrieve JSON data
521 via cURL. This can be used to collect values from CouchDB documents (which are
522 stored JSON notation), for example.
524 The following example will collect several values from the built-in `_stats'
525 runtime statistics module of CouchDB
526 (L<http://wiki.apache.org/couchdb/Runtime_Statistics>).
529 <URL "http://localhost:5984/_stats">
531 <Key "httpd/requests/count">
535 <Key "httpd_request_methods/*/count">
536 Type "http_request_methods"
539 <Key "httpd_status_codes/*/count">
540 Type "http_response_codes"
545 Another CouchDB example:
546 The following example will collect the status values from each database:
548 <URL "http://localhost:5984/_all_dbs">
553 <Key "*/doc_del_count">
561 In the B<Plugin> block, there may be one or more B<URL> blocks, each defining
562 a URL to be fetched via HTTP (using libcurl) and one or more B<Key> blocks.
563 The B<Key> string argument must be in a path format, of which is used to collect
564 a value from a JSON map object. If a B<Key> path element is that of a I<*> wildcard,
565 the values for all keys will be collectd.
567 The following options are valid within B<URL> blocks:
571 =item B<Instance> I<Instance>
573 Sets the plugin instance to I<Instance>.
575 =item B<User> I<Name>
577 Username to use if authorization is required to read the page.
579 =item B<Password> I<Password>
581 Password to use if authorization is required to read the page.
583 =item B<VerifyPeer> B<true>|B<false>
585 Enable or disable peer SSL certificate verification. See
586 L<http://curl.haxx.se/docs/sslcerts.html> for details. Enabled by default.
588 =item B<VerifyHost> B<true>|B<false>
590 Enable or disable peer host name verification. If enabled, the plugin checks if
591 the C<Common Name> or a C<Subject Alternate Name> field of the SSL certificate
592 matches the host name provided by the B<URL> option. If this identity check
593 fails, the connection is aborted. Obviously, only works when connecting to a
594 SSL enabled server. Enabled by default.
596 =item B<CACert> I<file>
598 File that holds one or more SSL certificates. If you want to use HTTPS you will
599 possibly need this option. What CA certificates come bundled with C<libcurl>
600 and are checked by default depends on the distribution you use.
604 The following options are valid within B<Key> blocks:
608 =item B<Type> I<Type>
610 Sets the type used to dispatch the values to the daemon. Detailed information
611 about types and their configuration can be found in L<types.db(5)>. This
614 =item B<Instance> I<Instance>
616 Type-instance to use. Defaults to the current map key or current string array element value.
622 This plugin uses the B<dbi> library (L<http://libdbi.sourceforge.net/>) to
623 connect to various databases, execute I<SQL> statements and read back the
624 results. I<dbi> is an acronym for "database interface" in case you were
625 wondering about the name. You can configure how each column is to be
626 interpreted and the plugin will generate one or more data sets from each row
627 returned according to these rules.
629 Because the plugin is very generic, the configuration is a little more complex
630 than those of other plugins. It usually looks something like this:
633 <Query "out_of_stock">
634 Statement "SELECT category, COUNT(*) AS value FROM products WHERE in_stock = 0 GROUP BY category"
635 # Use with MySQL 5.0.0 or later
639 InstancePrefix "out_of_stock"
640 InstancesFrom "category"
644 <Database "product_information">
646 DriverOption "host" "localhost"
647 DriverOption "username" "collectd"
648 DriverOption "password" "aZo6daiw"
649 DriverOption "dbname" "prod_info"
655 The configuration above defines one query with one result and one database. The
656 query is then linked to the database with the B<Query> option I<within> the
657 B<E<lt>DatabaseE<gt>> block. You can have any number of queries and databases
658 and you can also use the B<Include> statement to split up the configuration
659 file in multiple, smaller files. However, the B<E<lt>QueryE<gt>> block I<must>
660 precede the B<E<lt>DatabaseE<gt>> blocks, because the file is interpreted from
663 The following is a complete list of options:
665 =head3 B<Query> blocks
667 Query blocks define I<SQL> statements and how the returned data should be
668 interpreted. They are identified by the name that is given in the opening line
669 of the block. Thus the name needs to be unique. Other than that, the name is
670 not used in collectd.
672 In each B<Query> block, there is one or more B<Result> blocks. B<Result> blocks
673 define which column holds which value or instance information. You can use
674 multiple B<Result> blocks to create multiple values from one returned row. This
675 is especially useful, when queries take a long time and sending almost the same
676 query again and again is not desirable.
680 <Query "environment">
681 Statement "select station, temperature, humidity from environment"
684 # InstancePrefix "foo"
685 InstancesFrom "station"
686 ValuesFrom "temperature"
690 InstancesFrom "station"
691 ValuesFrom "humidity"
695 The following options are accepted:
699 =item B<Statement> I<SQL>
701 Sets the statement that should be executed on the server. This is B<not>
702 interpreted by collectd, but simply passed to the database server. Therefore,
703 the SQL dialect that's used depends on the server collectd is connected to.
705 The query has to return at least two columns, one for the instance and one
706 value. You cannot omit the instance, even if the statement is guaranteed to
707 always return exactly one line. In that case, you can usually specify something
710 Statement "SELECT \"instance\", COUNT(*) AS value FROM table"
712 (That works with MySQL but may not be valid SQL according to the spec. If you
713 use a more strict database server, you may have to select from a dummy table or
716 Please note that some databases, for example B<Oracle>, will fail if you
717 include a semicolon at the end of the statement.
719 =item B<MinVersion> I<Version>
721 =item B<MaxVersion> I<Value>
723 Only use this query for the specified database version. You can use these
724 options to provide multiple queries with the same name but with a slightly
725 different syntax. The plugin will use only those queries, where the specified
726 minimum and maximum versions fit the version of the database in use.
728 The database version is determined by C<dbi_conn_get_engine_version>, see the
729 L<libdbi documentation|http://libdbi.sourceforge.net/docs/programmers-guide/reference-conn.html#DBI-CONN-GET-ENGINE-VERSION>
730 for details. Basically, each part of the version is assumed to be in the range
731 from B<00> to B<99> and all dots are removed. So version "4.1.2" becomes
732 "40102", version "5.0.42" becomes "50042".
734 B<Warning:> The plugin will use B<all> matching queries, so if you specify
735 multiple queries with the same name and B<overlapping> ranges, weird stuff will
736 happen. Don't to it! A valid example would be something along these lines:
747 In the above example, there are three ranges that don't overlap. The last one
748 goes from version "5.1.0" to infinity, meaning "all later versions". Versions
749 before "4.0.0" are not specified.
751 =item B<Type> I<Type>
753 The B<type> that's used for each line returned. See L<types.db(5)> for more
754 details on how types are defined. In short: A type is a predefined layout of
755 data and the number of values and type of values has to match the type
758 If you specify "temperature" here, you need exactly one gauge column. If you
759 specify "if_octets", you will need two counter columns. See the B<ValuesFrom>
762 There must be exactly one B<Type> option inside each B<Result> block.
764 =item B<InstancePrefix> I<prefix>
766 Prepends I<prefix> to the type instance. If B<InstancesFrom> (see below) is not
767 given, the string is simply copied. If B<InstancesFrom> is given, I<prefix> and
768 all strings returned in the appropriate columns are concatenated together,
769 separated by dashes I<("-")>.
771 =item B<InstancesFrom> I<column0> [I<column1> ...]
773 Specifies the columns whose values will be used to create the "type-instance"
774 for each row. If you specify more than one column, the value of all columns
775 will be joined together with dashes I<("-")> as separation characters.
777 The plugin itself does not check whether or not all built instances are
778 different. It's your responsibility to assure that each is unique. This is
779 especially true, if you do not specify B<InstancesFrom>: B<You> have to make
780 sure that only one row is returned in this case.
782 If neither B<InstancePrefix> nor B<InstancesFrom> is given, the type-instance
785 =item B<ValuesFrom> I<column0> [I<column1> ...]
787 Names the columns whose content is used as the actual data for the data sets
788 that are dispatched to the daemon. How many such columns you need is determined
789 by the B<Type> setting above. If you specify too many or not enough columns,
790 the plugin will complain about that and no data will be submitted to the
793 The actual data type in the columns is not that important. The plugin will
794 automatically cast the values to the right type if it know how to do that. So
795 it should be able to handle integer an floating point types, as well as strings
796 (if they include a number at the beginning).
798 There must be at least one B<ValuesFrom> option inside each B<Result> block.
802 =head3 B<Database> blocks
804 Database blocks define a connection to a database and which queries should be
805 sent to that database. Since the used "dbi" library can handle a wide variety
806 of databases, the configuration is very generic. If in doubt, refer to libdbi's
807 documentationE<nbsp>- we stick as close to the terminology used there.
809 Each database needs a "name" as string argument in the starting tag of the
810 block. This name will be used as "PluginInstance" in the values submitted to
811 the daemon. Other than that, that name is not used.
815 =item B<Driver> I<Driver>
817 Specifies the driver to use to connect to the database. In many cases those
818 drivers are named after the database they can connect to, but this is not a
819 technical necessity. These drivers are sometimes referred to as "DBD",
820 B<D>ataB<B>ase B<D>river, and some distributions ship them in separate
821 packages. Drivers for the "dbi" library are developed by the B<libdbi-drivers>
822 project at L<http://libdbi-drivers.sourceforge.net/>.
824 You need to give the driver name as expected by the "dbi" library here. You
825 should be able to find that in the documentation for each driver. If you
826 mistype the driver name, the plugin will dump a list of all known driver names
829 =item B<DriverOption> I<Key> I<Value>
831 Sets driver-specific options. What option a driver supports can be found in the
832 documentation for each driver, somewhere at
833 L<http://libdbi-drivers.sourceforge.net/>. However, the options "host",
834 "username", "password", and "dbname" seem to be deE<nbsp>facto standards.
836 Unfortunately, drivers are not too keen to report errors when an unknown option
837 is passed to them, so invalid settings here may go unnoticed. This is not the
838 plugin's fault, it will report errors if it gets them from the libraryE<nbsp>/
839 the driver. If a driver complains about an option, the plugin will dump a
840 complete list of all options understood by that driver to the log.
842 =item B<SelectDB> I<Database>
844 In some cases, the database name you connect with is not the database name you
845 want to use for querying data. If this option is set, the plugin will "select"
846 (switch to) that database after the connection is established.
848 =item B<Query> I<QueryName>
850 Associates the query named I<QueryName> with this database connection. The
851 query needs to be defined I<before> this statement, i.E<nbsp>e. all query
852 blocks you want to refer to must be placed above the database block you want to
861 =item B<Device> I<Device>
863 Select partitions based on the devicename.
865 =item B<MountPoint> I<Directory>
867 Select partitions based on the mountpoint.
869 =item B<FSType> I<FSType>
871 Select partitions based on the filesystem type.
873 =item B<IgnoreSelected> I<true>|I<false>
875 Invert the selection: If set to true, all partitions B<except> the ones that
876 match any one of the criteria are collected. By default only selected
877 partitions are collected if a selection is made. If no selection is configured
878 at all, B<all> partitions are selected.
880 =item B<ReportByDevice> I<true>|I<false>
882 Report using the device name rather than the mountpoint. i.e. with this I<false>,
883 (the default), it will report a disk as "root", but with it I<true>, it will be
884 "sda1" (or whichever).
888 =head2 Plugin C<disk>
890 The C<disk> plugin collects information about the usage of physical disks and
891 logical disks (partitions). Values collected are the number of octets written
892 to and read from a disk or partition, the number of read/write operations
893 issued to the disk and a rather complex "time" it took for these commands to be
896 Using the following two options you can ignore some disks or configure the
897 collection only of specific disks.
901 =item B<Disk> I<Name>
903 Select the disk I<Name>. Whether it is collected or ignored depends on the
904 B<IgnoreSelected> setting, see below. As with other plugins that use the
905 daemon's ignorelist functionality, a string that starts and ends with a slash
906 is interpreted as a regular expression. Examples:
911 =item B<IgnoreSelected> B<true>|B<false>
913 Sets whether selected disks, i.E<nbsp>e. the ones matches by any of the B<Disk>
914 statements, are ignored or if all other disks are ignored. The behavior
915 (hopefully) is intuitive: If no B<Disk> option is configured, all disks are
916 collected. If at least one B<Disk> option is given and no B<IgnoreSelected> or
917 set to B<false>, B<only> matching disks will be collected. If B<IgnoreSelected>
918 is set to B<true>, all disks are collected B<except> the ones matched.
926 =item B<Interface> I<Interface>
928 The dns plugin uses B<libpcap> to capture dns traffic and analyses it. This
929 option sets the interface that should be used. If this option is not set, or
930 set to "any", the plugin will try to get packets from B<all> interfaces. This
931 may not work on certain platforms, such as MacE<nbsp>OSE<nbsp>X.
933 =item B<IgnoreSource> I<IP-address>
935 Ignore packets that originate from this address.
937 =item B<SelectNumericQueryTypes> B<true>|B<false>
939 Enabled by default, collects unknown (and thus presented as numeric only) query types.
943 =head2 Plugin C<email>
947 =item B<SocketFile> I<Path>
949 Sets the socket-file which is to be created.
951 =item B<SocketGroup> I<Group>
953 If running as root change the group of the UNIX-socket after it has been
954 created. Defaults to B<collectd>.
956 =item B<SocketPerms> I<Permissions>
958 Change the file permissions of the UNIX-socket after it has been created. The
959 permissions must be given as a numeric, octal value as you would pass to
960 L<chmod(1)>. Defaults to B<0770>.
962 =item B<MaxConns> I<Number>
964 Sets the maximum number of connections that can be handled in parallel. Since
965 this many threads will be started immediately setting this to a very high
966 value will waste valuable resources. Defaults to B<5> and will be forced to be
967 at most B<16384> to prevent typos and dumb mistakes.
971 =head2 Plugin C<exec>
973 Please make sure to read L<collectd-exec(5)> before using this plugin. It
974 contains valuable information on when the executable is executed and the
975 output that is expected from it.
979 =item B<Exec> I<User>[:[I<Group>]] I<Executable> [I<E<lt>argE<gt>> [I<E<lt>argE<gt>> ...]]
981 =item B<NotificationExec> I<User>[:[I<Group>]] I<Executable> [I<E<lt>argE<gt>> [I<E<lt>argE<gt>> ...]]
983 Execute the executable I<Executable> as user I<User>. If the user name is
984 followed by a colon and a group name, the effective group is set to that group.
985 The real group and saved-set group will be set to the default group of that
986 user. If no group is given the effective group ID will be the same as the real
989 Please note that in order to change the user and/or group the daemon needs
990 superuser privileges. If the daemon is run as an unprivileged user you must
991 specify the same user/group here. If the daemon is run with superuser
992 privileges, you must supply a non-root user here.
994 The executable may be followed by optional arguments that are passed to the
995 program. Please note that due to the configuration parsing numbers and boolean
996 values may be changed. If you want to be absolutely sure that something is
997 passed as-is please enclose it in quotes.
999 The B<Exec> and B<NotificationExec> statements change the semantics of the
1000 programs executed, i.E<nbsp>e. the data passed to them and the response
1001 expected from them. This is documented in great detail in L<collectd-exec(5)>.
1005 =head2 Plugin C<filecount>
1007 The C<filecount> plugin counts the number of files in a certain directory (and
1008 its subdirectories) and their combined size. The configuration is very straight
1011 <Plugin "filecount">
1012 <Directory "/var/qmail/queue/mess">
1013 Instance "qmail-message"
1015 <Directory "/var/qmail/queue/todo">
1016 Instance "qmail-todo"
1018 <Directory "/var/lib/php5">
1019 Instance "php5-sessions"
1024 The example above counts the number of files in QMail's queue directories and
1025 the number of PHP5 sessions. Jfiy: The "todo" queue holds the messages that
1026 QMail has not yet looked at, the "message" queue holds the messages that were
1027 classified into "local" and "remote".
1029 As you can see, the configuration consists of one or more C<Directory> blocks,
1030 each of which specifies a directory in which to count the files. Within those
1031 blocks, the following options are recognized:
1035 =item B<Instance> I<Instance>
1037 Sets the plugin instance to I<Instance>. That instance name must be unique, but
1038 it's your responsibility, the plugin doesn't check for that. If not given, the
1039 instance is set to the directory name with all slashes replaced by underscores
1040 and all leading underscores removed.
1042 =item B<Name> I<Pattern>
1044 Only count files that match I<Pattern>, where I<Pattern> is a shell-like
1045 wildcard as understood by L<fnmatch(3)>. Only the B<filename> is checked
1046 against the pattern, not the entire path. In case this makes it easier for you:
1047 This option has been named after the B<-name> parameter to L<find(1)>.
1049 =item B<MTime> I<Age>
1051 Count only files of a specific age: If I<Age> is greater than zero, only files
1052 that haven't been touched in the last I<Age> seconds are counted. If I<Age> is
1053 a negative number, this is inversed. For example, if B<-60> is specified, only
1054 files that have been modified in the last minute will be counted.
1056 The number can also be followed by a "multiplier" to easily specify a larger
1057 timespan. When given in this notation, the argument must in quoted, i.E<nbsp>e.
1058 must be passed as string. So the B<-60> could also be written as B<"-1m"> (one
1059 minute). Valid multipliers are C<s> (second), C<m> (minute), C<h> (hour), C<d>
1060 (day), C<w> (week), and C<y> (year). There is no "month" multiplier. You can
1061 also specify fractional numbers, e.E<nbsp>g. B<"0.5d"> is identical to
1064 =item B<Size> I<Size>
1066 Count only files of a specific size. When I<Size> is a positive number, only
1067 files that are at least this big are counted. If I<Size> is a negative number,
1068 this is inversed, i.E<nbsp>e. only files smaller than the absolute value of
1069 I<Size> are counted.
1071 As with the B<MTime> option, a "multiplier" may be added. For a detailed
1072 description see above. Valid multipliers here are C<b> (byte), C<k> (kilobyte),
1073 C<m> (megabyte), C<g> (gigabyte), C<t> (terabyte), and C<p> (petabyte). Please
1074 note that there are 1000 bytes in a kilobyte, not 1024.
1076 =item B<Recursive> I<true>|I<false>
1078 Controls whether or not to recurse into subdirectories. Enabled by default.
1082 =head2 Plugin C<GenericJMX>
1084 The I<GenericJMX plugin> is written in I<Java> and therefore documented in
1085 L<collectd-java(5)>.
1087 =head2 Plugin C<gmond>
1089 The I<gmond> plugin received the multicast traffic sent by B<gmond>, the
1090 statistics collection daemon of Ganglia. Mappings for the standard "metrics"
1091 are built-in, custom mappings may be added via B<Metric> blocks, see below.
1096 MCReceiveFrom "239.2.11.71" "8649"
1097 <Metric "swap_total">
1099 TypeInstance "total"
1102 <Metric "swap_free">
1109 The following metrics are built-in:
1115 load_one, load_five, load_fifteen
1119 cpu_user, cpu_system, cpu_idle, cpu_nice, cpu_wio
1123 mem_free, mem_shared, mem_buffers, mem_cached, mem_total
1135 Available configuration options:
1139 =item B<MCReceiveFrom> I<MCGroup> [I<Port>]
1141 Sets sets the multicast group and UDP port to which to subscribe.
1143 Default: B<239.2.11.71>E<nbsp>/E<nbsp>B<8649>
1145 =item E<lt>B<Metric> I<Name>E<gt>
1147 These blocks add a new metric conversion to the internal table. I<Name>, the
1148 string argument to the B<Metric> block, is the metric name as used by Ganglia.
1152 =item B<Type> I<Type>
1154 Type to map this metric to. Required.
1156 =item B<TypeInstance> I<Instance>
1158 Type-instance to use. Optional.
1160 =item B<DataSource> I<Name>
1162 Data source to map this metric to. If the configured type has exactly one data
1163 source, this is optional. Otherwise the option is required.
1169 =head2 Plugin C<hddtemp>
1171 To get values from B<hddtemp> collectd connects to B<localhost> (127.0.0.1),
1172 port B<7634/tcp>. The B<Host> and B<Port> options can be used to change these
1173 default values, see below. C<hddtemp> has to be running to work correctly. If
1174 C<hddtemp> is not running timeouts may appear which may interfere with other
1177 The B<hddtemp> homepage can be found at
1178 L<http://www.guzu.net/linux/hddtemp.php>.
1182 =item B<Host> I<Hostname>
1184 Hostname to connect to. Defaults to B<127.0.0.1>.
1186 =item B<Port> I<Port>
1188 TCP-Port to connect to. Defaults to B<7634>.
1190 =item B<TranslateDevicename> I<true>|I<false>
1192 If enabled, translate the disk names to major/minor device numbers
1193 (e.E<nbsp>g. "8-0" for /dev/sda). For backwards compatibility this defaults to
1194 I<true> but it's recommended to disable it as it will probably be removed in
1195 the next major version.
1199 =head2 Plugin C<interface>
1203 =item B<Interface> I<Interface>
1205 Select this interface. By default these interfaces will then be collected. For
1206 a more detailed description see B<IgnoreSelected> below.
1208 =item B<IgnoreSelected> I<true>|I<false>
1210 If no configuration if given, the B<traffic>-plugin will collect data from
1211 all interfaces. This may not be practical, especially for loopback- and
1212 similar interfaces. Thus, you can use the B<Interface>-option to pick the
1213 interfaces you're interested in. Sometimes, however, it's easier/preferred
1214 to collect all interfaces I<except> a few ones. This option enables you to
1215 do that: By setting B<IgnoreSelected> to I<true> the effect of
1216 B<Interface> is inverted: All selected interfaces are ignored and all
1217 other interfaces are collected.
1221 =head2 Plugin C<ipmi>
1225 =item B<Sensor> I<Sensor>
1227 Selects sensors to collect or to ignore, depending on B<IgnoreSelected>.
1229 =item B<IgnoreSelected> I<true>|I<false>
1231 If no configuration if given, the B<ipmi> plugin will collect data from all
1232 sensors found of type "temperature", "voltage", "current" and "fanspeed".
1233 This option enables you to do that: By setting B<IgnoreSelected> to I<true>
1234 the effect of B<Sensor> is inverted: All selected sensors are ignored and
1235 all other sensors are collected.
1237 =item B<NotifySensorAdd> I<true>|I<false>
1239 If a sensor appears after initialization time of a minute a notification
1242 =item B<NotifySensorRemove> I<true>|I<false>
1244 If a sensor disappears a notification is sent.
1246 =item B<NotifySensorNotPresent> I<true>|I<false>
1248 If you have for example dual power supply and one of them is (un)plugged then
1249 a notification is sent.
1253 =head2 Plugin C<iptables>
1257 =item B<Chain> I<Table> I<Chain> [I<Comment|Number> [I<Name>]]
1259 Select the rules to count. If only I<Table> and I<Chain> are given, this plugin
1260 will collect the counters of all rules which have a comment-match. The comment
1261 is then used as type-instance.
1263 If I<Comment> or I<Number> is given, only the rule with the matching comment or
1264 the I<n>th rule will be collected. Again, the comment (or the number) will be
1265 used as the type-instance.
1267 If I<Name> is supplied, it will be used as the type-instance instead of the
1268 comment or the number.
1272 =head2 Plugin C<irq>
1278 Select this irq. By default these irqs will then be collected. For a more
1279 detailed description see B<IgnoreSelected> below.
1281 =item B<IgnoreSelected> I<true>|I<false>
1283 If no configuration if given, the B<irq>-plugin will collect data from all
1284 irqs. This may not be practical, especially if no interrupts happen. Thus, you
1285 can use the B<Irq>-option to pick the interrupt you're interested in.
1286 Sometimes, however, it's easier/preferred to collect all interrupts I<except> a
1287 few ones. This option enables you to do that: By setting B<IgnoreSelected> to
1288 I<true> the effect of B<Irq> is inverted: All selected interrupts are ignored
1289 and all other interrupts are collected.
1293 =head2 Plugin C<java>
1295 The I<Java> plugin makes it possible to write extensions for collectd in Java.
1296 This section only discusses the syntax and semantic of the configuration
1297 options. For more in-depth information on the I<Java> plugin, please read
1298 L<collectd-java(5)>.
1303 JVMArg "-verbose:jni"
1304 JVMArg "-Djava.class.path=/opt/collectd/lib/collectd/bindings/java"
1305 LoadPlugin "org.collectd.java.Foobar"
1306 <Plugin "org.collectd.java.Foobar">
1307 # To be parsed by the plugin
1311 Available configuration options:
1315 =item B<JVMArg> I<Argument>
1317 Argument that is to be passed to the I<Java Virtual Machine> (JVM). This works
1318 exactly the way the arguments to the I<java> binary on the command line work.
1319 Execute C<javaE<nbsp>--help> for details.
1321 Please note that B<all> these options must appear B<before> (i.E<nbsp>e. above)
1322 any other options! When another option is found, the JVM will be started and
1323 later options will have to be ignored!
1325 =item B<LoadPlugin> I<JavaClass>
1327 Instantiates a new I<JavaClass> object. The constructor of this object very
1328 likely then registers one or more callback methods with the server.
1330 See L<collectd-java(5)> for details.
1332 When the first such option is found, the virtual machine (JVM) is created. This
1333 means that all B<JVMArg> options must appear before (i.E<nbsp>e. above) all
1334 B<LoadPlugin> options!
1336 =item B<Plugin> I<Name>
1338 The entire block is passed to the Java plugin as an
1339 I<org.collectd.api.OConfigItem> object.
1341 For this to work, the plugin has to register a configuration callback first,
1342 see L<collectd-java(5)/"config callback">. This means, that the B<Plugin> block
1343 must appear after the appropriate B<LoadPlugin> block. Also note, that I<Name>
1344 depends on the (Java) plugin registering the callback and is completely
1345 independent from the I<JavaClass> argument passed to B<LoadPlugin>.
1349 =head2 Plugin C<libvirt>
1351 This plugin allows CPU, disk and network load to be collected for virtualized
1352 guests on the machine. This means that these characteristics can be collected
1353 for guest systems without installing any software on them - collectd only runs
1354 on the hosting system. The statistics are collected through libvirt
1355 (L<http://libvirt.org/>).
1357 Only I<Connection> is required.
1361 =item B<Connection> I<uri>
1363 Connect to the hypervisor given by I<uri>. For example if using Xen use:
1365 Connection "xen:///"
1367 Details which URIs allowed are given at L<http://libvirt.org/uri.html>.
1369 =item B<RefreshInterval> I<seconds>
1371 Refresh the list of domains and devices every I<seconds>. The default is 60
1372 seconds. Setting this to be the same or smaller than the I<Interval> will cause
1373 the list of domains and devices to be refreshed on every iteration.
1375 Refreshing the devices in particular is quite a costly operation, so if your
1376 virtualization setup is static you might consider increasing this. If this
1377 option is set to 0, refreshing is disabled completely.
1379 =item B<Domain> I<name>
1381 =item B<BlockDevice> I<name:dev>
1383 =item B<InterfaceDevice> I<name:dev>
1385 =item B<IgnoreSelected> I<true>|I<false>
1387 Select which domains and devices are collected.
1389 If I<IgnoreSelected> is not given or I<false> then only the listed domains and
1390 disk/network devices are collected.
1392 If I<IgnoreSelected> is I<true> then the test is reversed and the listed
1393 domains and disk/network devices are ignored, while the rest are collected.
1395 The domain name and device names may use a regular expression, if the name is
1396 surrounded by I</.../> and collectd was compiled with support for regexps.
1398 The default is to collect statistics for all domains and all their devices.
1402 BlockDevice "/:hdb/"
1403 IgnoreSelected "true"
1405 Ignore all I<hdb> devices on any domain, but other block devices (eg. I<hda>)
1408 =item B<HostnameFormat> B<name|uuid|hostname|...>
1410 When the libvirt plugin logs data, it sets the hostname of the collected data
1411 according to this setting. The default is to use the guest name as provided by
1412 the hypervisor, which is equal to setting B<name>.
1414 B<uuid> means use the guest's UUID. This is useful if you want to track the
1415 same guest across migrations.
1417 B<hostname> means to use the global B<Hostname> setting, which is probably not
1418 useful on its own because all guests will appear to have the same name.
1420 You can also specify combinations of these fields. For example B<name uuid>
1421 means to concatenate the guest name and UUID (with a literal colon character
1422 between, thus I<"foo:1234-1234-1234-1234">).
1426 =head2 Plugin C<logfile>
1430 =item B<LogLevel> B<debug|info|notice|warning|err>
1432 Sets the log-level. If, for example, set to B<notice>, then all events with
1433 severity B<notice>, B<warning>, or B<err> will be written to the logfile.
1435 Please note that B<debug> is only available if collectd has been compiled with
1438 =item B<File> I<File>
1440 Sets the file to write log messages to. The special strings B<stdout> and
1441 B<stderr> can be used to write to the standard output and standard error
1442 channels, respectively. This, of course, only makes much sense when collectd is
1443 running in foreground- or non-daemon-mode.
1445 =item B<Timestamp> B<true>|B<false>
1447 Prefix all lines printed by the current time. Defaults to B<true>.
1451 B<Note>: There is no need to notify the daemon after moving or removing the
1452 log file (e.E<nbsp>g. when rotating the logs). The plugin reopens the file
1453 for each line it writes.
1455 =head2 Plugin C<mbmon>
1457 The C<mbmon plugin> uses mbmon to retrieve temperature, voltage, etc.
1459 Be default collectd connects to B<localhost> (127.0.0.1), port B<411/tcp>. The
1460 B<Host> and B<Port> options can be used to change these values, see below.
1461 C<mbmon> has to be running to work correctly. If C<mbmon> is not running
1462 timeouts may appear which may interfere with other statistics..
1464 C<mbmon> must be run with the -r option ("print TAG and Value format");
1465 Debian's F</etc/init.d/mbmon> script already does this, other people
1466 will need to ensure that this is the case.
1470 =item B<Host> I<Hostname>
1472 Hostname to connect to. Defaults to B<127.0.0.1>.
1474 =item B<Port> I<Port>
1476 TCP-Port to connect to. Defaults to B<411>.
1480 =head2 Plugin C<memcachec>
1482 The C<memcachec plugin> connects to a memcached server, queries one or more
1483 given I<pages> and parses the returned data according to user specification.
1484 The I<matches> used are the same as the matches used in the C<curl> and C<tail>
1487 In order to talk to the memcached server, this plugin uses the I<libmemcached>
1488 library. Please note that there is another library with a very similar name,
1489 libmemcache (notice the missing `d'), which is not applicable.
1491 Synopsis of the configuration:
1493 <Plugin "memcachec">
1494 <Page "plugin_instance">
1498 Regex "(\\d+) bytes sent"
1501 Instance "type_instance"
1506 The configuration options are:
1510 =item E<lt>B<Page> I<Name>E<gt>
1512 Each B<Page> block defines one I<page> to be queried from the memcached server.
1513 The block requires one string argument which is used as I<plugin instance>.
1515 =item B<Server> I<Address>
1517 Sets the server address to connect to when querying the page. Must be inside a
1522 When connected to the memcached server, asks for the page I<Key>.
1524 =item E<lt>B<Match>E<gt>
1526 Match blocks define which strings to look for and how matches substrings are
1527 interpreted. For a description of match blocks, please see L<"Plugin tail">.
1531 =head2 Plugin C<memcached>
1533 The C<memcached plugin> connects to a memcached server and queries statistics
1534 about cache utilization, memory and bandwidth used.
1535 L<http://www.danga.com/memcached/>
1539 =item B<Host> I<Hostname>
1541 Hostname to connect to. Defaults to B<127.0.0.1>.
1543 =item B<Port> I<Port>
1545 TCP-Port to connect to. Defaults to B<11211>.
1549 =head2 Plugin C<mysql>
1551 The C<mysql plugin> requires B<mysqlclient> to be installed. It connects to
1552 one or more databases when started and keeps the connection up as long as
1553 possible. When the connection is interrupted for whatever reason it will try
1554 to re-connect. The plugin will complaint loudly in case anything goes wrong.
1556 This plugin issues the MySQL C<SHOW STATUS> / C<SHOW GLOBAL STATUS> command
1557 and collects information about MySQL network traffic, executed statements,
1558 requests, the query cache and threads by evaluating the
1559 C<Bytes_{received,sent}>, C<Com_*>, C<Handler_*>, C<Qcache_*> and C<Threads_*>
1560 return values. Please refer to the B<MySQL reference manual>, I<5.1.6. Server
1561 Status Variables> for an explanation of these values.
1563 Optionally, master and slave statistics may be collected in a MySQL
1564 replication setup. In that case, information about the synchronization state
1565 of the nodes are collected by evaluating the C<Position> return value of the
1566 C<SHOW MASTER STATUS> command and the C<Seconds_Behind_Master>,
1567 C<Read_Master_Log_Pos> and C<Exec_Master_Log_Pos> return values of the
1568 C<SHOW SLAVE STATUS> command. See the B<MySQL reference manual>,
1569 I<12.5.5.21 SHOW MASTER STATUS Syntax> and
1570 I<12.5.5.31 SHOW SLAVE STATUS Syntax> for details.
1585 Socket "/var/run/mysql/mysqld.sock"
1587 SlaveNotifications true
1591 A B<Database> block defines one connection to a MySQL database. It accepts a
1592 single argument which specifies the name of the database. None of the other
1593 options are required. MySQL will use default values as documented in the
1594 section "mysql_real_connect()" in the B<MySQL reference manual>.
1598 =item B<Host> I<Hostname>
1600 Hostname of the database server. Defaults to B<localhost>.
1602 =item B<User> I<Username>
1604 Username to use when connecting to the database. The user does not have to be
1605 granted any privileges (which is synonym to granting the C<USAGE> privilege).
1606 Any existing MySQL user will do.
1608 =item B<Password> I<Password>
1610 Password needed to log into the database.
1612 =item B<Database> I<Database>
1614 Select this database. Defaults to I<no database> which is a perfectly reasonable
1615 option for what this plugin does.
1617 =item B<Port> I<Port>
1619 TCP-port to connect to. The port must be specified in its numeric form, but it
1620 must be passed as a string nonetheless. For example:
1624 If B<Host> is set to B<localhost> (the default), this setting has no effect.
1625 See the documentation for the C<mysql_real_connect> function for details.
1627 =item B<Socket> I<Socket>
1629 Specifies the path to the UNIX domain socket of the MySQL server. This option
1630 only has any effect, if B<Host> is set to B<localhost> (the default).
1631 Otherwise, use the B<Port> option above. See the documentation for the
1632 C<mysql_real_connect> function for details.
1634 =item B<MasterStats> I<true|false>
1636 =item B<SlaveStats> I<true|false>
1638 Enable the collection of master / slave statistics in a replication setup.
1640 =item B<SlaveNotifications> I<true|false>
1642 If enabled, the plugin sends a notification if the replication slave I/O and /
1643 or SQL threads are not running.
1647 =head2 Plugin C<netapp>
1649 The netapp plugin can collect various performance and capacity informations
1650 from a NetApp filer using the NetApp API.
1652 To collect these data collectd will log in to the NetApp via HTTP(S) and HTTP
1653 basic authentication.
1655 B<Do not use a regular user for this!> Create a special collectd user with just
1656 the minimum of capabilities needed. The user only needs the "login-http-admin"
1657 capability as well as a few more depending on which data will be collected.
1658 Required capabilities are documented below.
1663 <Host "netapp1.example.com">
1671 </GetSystemPerfData>
1679 </GetVolumePerfData>
1685 The netapp plugin accepts the following configuration options:
1689 =item B<Host> I<Name>
1691 A host block defines one NetApp filer. It will appear in collectd with the name
1692 you specify here which does not have to be its real name nor its hostname.
1694 =item B<Protocol> B<httpd>|B<http>
1696 The protocol collectd will use to query this host.
1704 Valid options: http, https
1706 =item B<Address> I<Address>
1708 The hostname or IP address of the host.
1714 Default: The "host" block's name.
1716 =item B<Port> I<Port>
1718 The TCP port to connect to on the host.
1724 Default: 80 for protocol "http", 443 for protocol "https"
1726 =item B<User> I<User>
1728 =item B<Password> I<Password>
1730 The username and password to use to login to the NetApp.
1736 =item B<Interval> I<Interval>
1742 The following options decide what kind of data will be collected. You can
1743 either use them as a block and fine tune various parameters inside this block,
1744 use them as a single statement to just accept all default values, or omit it to
1745 not collect any data.
1747 The following options are valid inside all blocks:
1751 =item B<Multiplier> I<Multiplier>
1753 The host specific interval between data collections is multiplied by this value
1754 for collecting these data.
1764 =head3 The GetSystemPerfData block
1766 This will collect various performance data about the whole system.
1768 B<Note:> To get this data the collectd user needs the
1769 "api-perf-object-get-instances" capability.
1773 =item B<GetCPULoad> B<true>|B<false>
1775 If you set this option to true the current CPU usage will be read. This will be
1776 the average usage between all CPUs in your NetApp without any information about
1779 B<Note:> These are the same values that the NetApp CLI command "sysstat"
1780 returns in the "CPU" field.
1788 Result: Two value lists of type "cpu", and type instances "idle" and "system".
1790 =item B<GetInterfaces> B<true>|B<false>
1792 If you set this option to true the current traffic of the network interfaces
1793 will be read. This will be the total traffic over all interfaces of your NetApp
1794 without any information about individual interfaces.
1796 B<Note:> This is the same values that the NetApp CLI command "sysstat" returns
1797 in the "Net kB/s" field.
1807 Result: One value list of type "if_octects".
1809 =item B<GetDiskIO> B<true>|B<false>
1811 If you set this option to true the current IO throughput will be read. This
1812 will be the total IO of your NetApp without any information about individual
1813 disks, volumes or aggregates.
1815 B<Note:> This is the same values that the NetApp CLI command "sysstat" returns
1816 in the "DiskE<nbsp>kB/s" field.
1824 Result: One value list of type "disk_octets".
1826 =item B<GetDiskOps> B<true>|B<false>
1828 If you set this option to true the current number of HTTP, NFS, CIFS, FCP,
1829 iSCSI, etc. operations will be read. This will be the total number of
1830 operations on your NetApp without any information about individual volumes or
1833 B<Note:> These are the same values that the NetApp CLI command "sysstat"
1834 returns in the "NFS", "CIFS", "HTTP", "FCP" and "iSCSI" fields.
1842 Result: A variable number of value lists of type "disk_ops_complex". Each type
1843 of operation will result in one value list with the name of the operation as
1848 =head3 The GetWaflPerfData block
1850 This will collect various performance data about the WAFL file system. At the
1851 moment this just means cache performance.
1853 B<Note:> To get this data the collectd user needs the
1854 "api-perf-object-get-instances" capability.
1856 B<Note:> The interface to get these values is classified as "Diagnostics" by
1857 NetApp. This means that it is not guaranteed to be stable even between minor
1862 =item B<GetNameCache> B<true>|B<false>
1870 Result: One value list of type "cache_ratio" and type instance
1873 =item B<GetDirCache> B<true>|B<false>
1881 Result: One value list of type "cache_ratio" and type instance "find_dir_hit".
1883 =item B<GetInodeCache> B<true>|B<false>
1891 Result: One value list of type "cache_ratio" and type instance
1894 =item B<GetBufCache> B<true>|B<false>
1896 B<Note:> This is the same value that the NetApp CLI command "sysstat" returns
1897 in the "Cache hit" field.
1905 Result: One value list of type "cache_ratio" and type instance "buf_hash_hit".
1909 =head3 The Disks block
1911 This will collect performance data about the individual disks in the NetApp.
1913 B<Note:> To get this data the collectd user needs the
1914 "api-perf-object-get-instances" capability.
1918 =item B<Interval> I<Seconds>
1920 Collect disk statistics every I<Seconds> seconds.
1922 =item B<GetBusy> B<true>|B<false>
1924 If you set this option to true the busy time of all disks will be calculated
1925 and the value of the busiest disk in the system will be written.
1927 B<Note:> This is the same values that the NetApp CLI command "sysstat" returns
1928 in the "Disk util" field. Probably.
1936 Result: One value list of type "percent" and type instance "disk_busy".
1940 =head3 The GetVolumePerfData block
1942 This will collect various performance data about the individual volumes.
1944 All of these options take a list of volumes as parameters. In this case
1945 "volume" means just the name of the volume, without the "/vol/" prefix or
1948 The special values "-" and "+" are supported. "-" means "don't collect values
1949 for any volumes". "+" means "collect values for all volumes, even volumes that
1950 are created after collectd was started." Additionally you can prefix a volume
1951 name with a "-" sign to exclude this one volume. Eg '"+" "-vol0"' collectes
1952 values for all volumes except vol0. The order of the parameters is important.
1953 '"-vol0" "+"' doesn't make sense because the "+" overrides the earlier "-vol0".
1955 B<Note:> To get this data the collectd user needs the
1956 "api-perf-object-get-instances" capability.
1960 =item B<GetIO> I<Volume> [I<Volume> ...]
1961 The current IO throughput will be read for every volume specified here.
1965 Type: list of strings
1969 Result: Data sources of type "disk_octets" and the name of the volume as
1972 =item B<GetOps> I<Volume> [I<Volume> ...]
1974 The current number of operation will be read for every volume specified here.
1978 Type: list of strings
1982 Result: Data sources of type "disk_ops" and the name of the volume as
1985 =item B<GetLatency> I<Volume> [I<Volume> ...]
1987 The current latency for volume access in microseconds will be read for every
1988 volume specified here.
1992 Type: list of strings
1996 Result: Data sources of type "disk_latency" and the name of the volume as
2001 =head3 The GetVolumeData block
2003 This will collect capacity data about the individual volumes.
2005 All of these options take a list of volumes as parameters, just like the
2006 GetVolumePerfData options.
2008 B<Note:> To get this data the collectd user needs the "api-volume-list-info"
2013 =item B<GetDiskUtil>
2015 The current capacity of the volume will be collected. This will result in two
2016 to four value lists, depending on the configuration of the volume. All data
2017 sources are of type "df_complex" with the name of the volume as
2020 There will be type_instances "used" and "free" for the number of used and
2021 available bytes on the volume. If the volume has some space reserved for
2022 snapshots, a type_instance "snap_reserved" will be available. If the volume
2023 has SIS enabled, a type_instance "sis_saved" will be available. This is the
2024 number of bytes saved by the SIS feature.
2026 B<Note:> The current NetApp API has a bug that results in this value being
2027 reported as a 32E<nbsp>bit number. This plugin tries to guess the correct
2028 number which works most of the time. If you see strange values here, bug
2029 NetApp support to fix this.
2033 Type: list of strings
2037 =item B<GetSnapData>
2043 =head2 Plugin C<netlink>
2045 The C<netlink> plugin uses a netlink socket to query the Linux kernel about
2046 statistics of various interface and routing aspects.
2050 =item B<Interface> I<Interface>
2052 =item B<VerboseInterface> I<Interface>
2054 Instruct the plugin to collect interface statistics. This is basically the same
2055 as the statistics provided by the C<interface> plugin (see above) but
2056 potentially much more detailed.
2058 When configuring with B<Interface> only the basic statistics will be collected,
2059 namely octets, packets, and errors. These statistics are collected by
2060 the C<interface> plugin, too, so using both at the same time is no benefit.
2062 When configured with B<VerboseInterface> all counters B<except> the basic ones,
2063 so that no data needs to be collected twice if you use the C<interface> plugin.
2064 This includes dropped packets, received multicast packets, collisions and a
2065 whole zoo of differentiated RX and TX errors. You can try the following command
2066 to get an idea of what awaits you:
2070 If I<Interface> is B<All>, all interfaces will be selected.
2072 =item B<QDisc> I<Interface> [I<QDisc>]
2074 =item B<Class> I<Interface> [I<Class>]
2076 =item B<Filter> I<Interface> [I<Filter>]
2078 Collect the octets and packets that pass a certain qdisc, class or filter.
2080 QDiscs and classes are identified by their type and handle (or classid).
2081 Filters don't necessarily have a handle, therefore the parent's handle is used.
2082 The notation used in collectd differs from that used in tc(1) in that it
2083 doesn't skip the major or minor number if it's zero and doesn't print special
2084 ids by their name. So, for example, a qdisc may be identified by
2085 C<pfifo_fast-1:0> even though the minor number of B<all> qdiscs is zero and
2086 thus not displayed by tc(1).
2088 If B<QDisc>, B<Class>, or B<Filter> is given without the second argument,
2089 i.E<nbsp>.e. without an identifier, all qdiscs, classes, or filters that are
2090 associated with that interface will be collected.
2092 Since a filter itself doesn't necessarily have a handle, the parent's handle is
2093 used. This may lead to problems when more than one filter is attached to a
2094 qdisc or class. This isn't nice, but we don't know how this could be done any
2095 better. If you have a idea, please don't hesitate to tell us.
2097 As with the B<Interface> option you can specify B<All> as the interface,
2098 meaning all interfaces.
2100 Here are some examples to help you understand the above text more easily:
2103 VerboseInterface "All"
2104 QDisc "eth0" "pfifo_fast-1:0"
2106 Class "ppp0" "htb-1:10"
2107 Filter "ppp0" "u32-1:0"
2110 =item B<IgnoreSelected>
2112 The behaviour is the same as with all other similar plugins: If nothing is
2113 selected at all, everything is collected. If some things are selected using the
2114 options described above, only these statistics are collected. If you set
2115 B<IgnoreSelected> to B<true>, this behavior is inverted, i.E<nbsp>e. the
2116 specified statistics will not be collected.
2120 =head2 Plugin C<network>
2122 The Network plugin sends data to a remote instance of collectd, receives data
2123 from a remote instance, or both at the same time. Data which has been received
2124 from the network is usually not transmitted again, but this can be actived, see
2125 the B<Forward> option below.
2127 The default IPv6 multicast group is C<ff18::efc0:4a42>. The default IPv4
2128 multicast group is C<239.192.74.66>. The default I<UDP> port is B<25826>.
2130 Both, B<Server> and B<Listen> can be used as single option or as block. When
2131 used as block, given options are valid for this socket only. For example:
2134 Server "collectd.internal.tld"
2135 <Server "collectd.external.tld">
2136 SecurityLevel "sign"
2137 Username "myhostname"
2144 =item B<E<lt>Server> I<Host> [I<Port>]B<E<gt>>
2146 The B<Server> statement/block sets the server to send datagrams to. The
2147 statement may occur multiple times to send each datagram to multiple
2150 The argument I<Host> may be a hostname, an IPv4 address or an IPv6 address. The
2151 optional second argument specifies a port number or a service name. If not
2152 given, the default, B<25826>, is used.
2154 The following options are recognized within B<Server> blocks:
2158 =item B<SecurityLevel> B<Encrypt>|B<Sign>|B<None>
2160 Set the security you require for network communication. When the security level
2161 has been set to B<Encrypt>, data sent over the network will be encrypted using
2162 I<AES-256>. The integrity of encrypted packets is ensured using I<SHA-1>. When
2163 set to B<Sign>, transmitted data is signed using the I<HMAC-SHA-256> message
2164 authentication code. When set to B<None>, data is sent without any security.
2166 This feature is only available if the I<network> plugin was linked with
2169 =item B<Username> I<Username>
2171 Sets the username to transmit. This is used by the server to lookup the
2172 password. See B<AuthFile> below. All security levels except B<None> require
2175 This feature is only available if the I<network> plugin was linked with
2178 =item B<Password> I<Password>
2180 Sets a password (shared secret) for this socket. All security levels except
2181 B<None> require this setting.
2183 This feature is only available if the I<network> plugin was linked with
2188 =item B<E<lt>Listen> I<Host> [I<Port>]B<E<gt>>
2190 The B<Listen> statement sets the interfaces to bind to. When multiple
2191 statements are found the daemon will bind to multiple interfaces.
2193 The argument I<Host> may be a hostname, an IPv4 address or an IPv6 address. If
2194 the argument is a multicast address the daemon will join that multicast group.
2195 The optional second argument specifies a port number or a service name. If not
2196 given, the default, B<25826>, is used.
2198 The following options are recognized within C<E<lt>ListenE<gt>> blocks:
2202 =item B<SecurityLevel> B<Encrypt>|B<Sign>|B<None>
2204 Set the security you require for network communication. When the security level
2205 has been set to B<Encrypt>, only encrypted data will be accepted. The integrity
2206 of encrypted packets is ensured using I<SHA-1>. When set to B<Sign>, only
2207 signed and encrypted data is accepted. When set to B<None>, all data will be
2208 accepted. If an B<AuthFile> option was given (see below), encrypted data is
2209 decrypted if possible.
2211 This feature is only available if the I<network> plugin was linked with
2214 =item B<AuthFile> I<Filename>
2216 Sets a file in which usernames are mapped to passwords. These passwords are
2217 used to verify signatures and to decrypt encrypted network packets. If
2218 B<SecurityLevel> is set to B<None>, this is optional. If given, signed data is
2219 verified and encrypted packets are decrypted. Otherwise, signed data is
2220 accepted without checking the signature and encrypted data cannot be decrypted.
2221 For the other security levels this option is mandatory.
2223 The file format is very simple: Each line consists of a username followed by a
2224 colon and any number of spaces followed by the password. To demonstrate, an
2225 example file could look like this:
2230 Each time a packet is received, the modification time of the file is checked
2231 using L<stat(2)>. If the file has been changed, the contents is re-read. While
2232 the file is being read, it is locked using L<fcntl(2)>.
2236 =item B<TimeToLive> I<1-255>
2238 Set the time-to-live of sent packets. This applies to all, unicast and
2239 multicast, and IPv4 and IPv6 packets. The default is to not change this value.
2240 That means that multicast packets will be sent with a TTL of C<1> (one) on most
2243 =item B<MaxPacketSize> I<1024-65535>
2245 Set the maximum size for datagrams received over the network. Packets larger
2246 than this will be truncated.
2248 =item B<Forward> I<true|false>
2250 If set to I<true>, write packets that were received via the network plugin to
2251 the sending sockets. This should only be activated when the B<Listen>- and
2252 B<Server>-statements differ. Otherwise packets may be send multiple times to
2253 the same multicast group. While this results in more network traffic than
2254 necessary it's not a huge problem since the plugin has a duplicate detection,
2255 so the values will not loop.
2257 =item B<CacheFlush> I<Seconds>
2259 For each host/plugin/type combination the C<network plugin> caches the time of
2260 the last value being sent or received. Every I<Seconds> seconds the plugin
2261 searches and removes all entries that are older than I<Seconds> seconds, thus
2262 freeing the unused memory again. Since this process is somewhat expensive and
2263 normally doesn't do much, this value should not be too small. The default is
2264 1800 seconds, but setting this to 86400 seconds (one day) will not do much harm
2269 =head2 Plugin C<nginx>
2271 This plugin collects the number of connections and requests handled by the
2272 C<nginx daemon> (speak: engineE<nbsp>X), a HTTP and mail server/proxy. It
2273 queries the page provided by the C<ngx_http_stub_status_module> module, which
2274 isn't compiled by default. Please refer to
2275 L<http://wiki.codemongers.com/NginxStubStatusModule> for more information on
2276 how to compile and configure nginx and this module.
2278 The following options are accepted by the C<nginx plugin>:
2282 =item B<URL> I<http://host/nginx_status>
2284 Sets the URL of the C<ngx_http_stub_status_module> output.
2286 =item B<User> I<Username>
2288 Optional user name needed for authentication.
2290 =item B<Password> I<Password>
2292 Optional password needed for authentication.
2294 =item B<VerifyPeer> B<true|false>
2296 Enable or disable peer SSL certificate verification. See
2297 L<http://curl.haxx.se/docs/sslcerts.html> for details. Enabled by default.
2299 =item B<VerifyHost> B<true|false>
2301 Enable or disable peer host name verification. If enabled, the plugin checks
2302 if the C<Common Name> or a C<Subject Alternate Name> field of the SSL
2303 certificate matches the host name provided by the B<URL> option. If this
2304 identity check fails, the connection is aborted. Obviously, only works when
2305 connecting to a SSL enabled server. Enabled by default.
2307 =item B<CACert> I<File>
2309 File that holds one or more SSL certificates. If you want to use HTTPS you will
2310 possibly need this option. What CA certificates come bundled with C<libcurl>
2311 and are checked by default depends on the distribution you use.
2315 =head2 Plugin C<notify_desktop>
2317 This plugin sends a desktop notification to a notification daemon, as defined
2318 in the Desktop Notification Specification. To actually display the
2319 notifications, B<notification-daemon> is required and B<collectd> has to be
2320 able to access the X server.
2322 The Desktop Notification Specification can be found at
2323 L<http://www.galago-project.org/specs/notification/>.
2327 =item B<OkayTimeout> I<timeout>
2329 =item B<WarningTimeout> I<timeout>
2331 =item B<FailureTimeout> I<timeout>
2333 Set the I<timeout>, in milliseconds, after which to expire the notification
2334 for C<OKAY>, C<WARNING> and C<FAILURE> severities respectively. If zero has
2335 been specified, the displayed notification will not be closed at all - the
2336 user has to do so herself. These options default to 5000. If a negative number
2337 has been specified, the default is used as well.
2341 =head2 Plugin C<notify_email>
2343 The I<notify_email> plugin uses the I<ESMTP> library to send notifications to a
2344 configured email address.
2346 I<libESMTP> is available from L<http://www.stafford.uklinux.net/libesmtp/>.
2348 Available configuration options:
2352 =item B<From> I<Address>
2354 Email address from which the emails should appear to come from.
2356 Default: C<root@localhost>
2358 =item B<Recipient> I<Address>
2360 Configures the email address(es) to which the notifications should be mailed.
2361 May be repeated to send notifications to multiple addresses.
2363 At least one B<Recipient> must be present for the plugin to work correctly.
2365 =item B<SMTPServer> I<Hostname>
2367 Hostname of the SMTP server to connect to.
2369 Default: C<localhost>
2371 =item B<SMTPPort> I<Port>
2373 TCP port to connect to.
2377 =item B<SMTPUser> I<Username>
2379 Username for ASMTP authentication. Optional.
2381 =item B<SMTPPassword> I<Password>
2383 Password for ASMTP authentication. Optional.
2385 =item B<Subject> I<Subject>
2387 Subject-template to use when sending emails. There must be exactly two
2388 string-placeholders in the subject, given in the standard I<printf(3)> syntax,
2389 i.E<nbsp>e. C<%s>. The first will be replaced with the severity, the second
2392 Default: C<Collectd notify: %s@%s>
2396 =head2 Plugin C<ntpd>
2400 =item B<Host> I<Hostname>
2402 Hostname of the host running B<ntpd>. Defaults to B<localhost>.
2404 =item B<Port> I<Port>
2406 UDP-Port to connect to. Defaults to B<123>.
2408 =item B<ReverseLookups> B<true>|B<false>
2410 Sets wether or not to perform reverse lookups on peers. Since the name or
2411 IP-address may be used in a filename it is recommended to disable reverse
2412 lookups. The default is to do reverse lookups to preserve backwards
2413 compatibility, though.
2417 =head2 Plugin C<nut>
2421 =item B<UPS> I<upsname>B<@>I<hostname>[B<:>I<port>]
2423 Add a UPS to collect data from. The format is identical to the one accepted by
2428 =head2 Plugin C<olsrd>
2430 The I<olsrd> plugin connects to the TCP port opened by the I<txtinfo> plugin of
2431 the Optimized Link State Routing daemon and reads information about the current
2432 state of the meshed network.
2434 The following configuration options are understood:
2438 =item B<Host> I<Host>
2440 Connect to I<Host>. Defaults to B<"localhost">.
2442 =item B<Port> I<Port>
2444 Specifies the port to connect to. This must be a string, even if you give the
2445 port as a number rather than a service name. Defaults to B<"2006">.
2447 =item B<CollectLinks> B<No>|B<Summary>|B<Detail>
2449 Specifies what information to collect about links, i.E<nbsp>e. direct
2450 connections of the daemon queried. If set to B<No>, no information is
2451 collected. If set to B<Summary>, the number of links and the average of all
2452 I<link quality> (LQ) and I<neighbor link quality> (NLQ) values is calculated.
2453 If set to B<Detail> LQ and NLQ are collected per link.
2455 Defaults to B<Detail>.
2457 =item B<CollectRoutes> B<No>|B<Summary>|B<Detail>
2459 Specifies what information to collect about routes of the daemon queried. If
2460 set to B<No>, no information is collected. If set to B<Summary>, the number of
2461 routes and the average I<metric> and I<ETX> is calculated. If set to B<Detail>
2462 metric and ETX are collected per route.
2464 Defaults to B<Summary>.
2466 =item B<CollectTopology> B<No>|B<Summary>|B<Detail>
2468 Specifies what information to collect about the global topology. If set to
2469 B<No>, no information is collected. If set to B<Summary>, the number of links
2470 in the entire topology and the average I<link quality> (LQ) is calculated.
2471 If set to B<Detail> LQ and NLQ are collected for each link in the entire topology.
2473 Defaults to B<Summary>.
2477 =head2 Plugin C<onewire>
2479 B<EXPERIMENTAL!> See notes below.
2481 The C<onewire> plugin uses the B<owcapi> library from the B<owfs> project
2482 L<http://owfs.org/> to read sensors connected via the onewire bus.
2484 Currently only temperature sensors (sensors with the family code C<10>,
2485 e.E<nbsp>g. DS1820, DS18S20, DS1920) can be read. If you have other sensors you
2486 would like to have included, please send a sort request to the mailing list.
2488 Hubs (the DS2409 chips) are working, but read the note, why this plugin is
2489 experimental, below.
2493 =item B<Device> I<Device>
2495 Sets the device to read the values from. This can either be a "real" hardware
2496 device, such as a serial port or an USB port, or the address of the
2497 L<owserver(1)> socket, usually B<localhost:4304>.
2499 Though the documentation claims to automatically recognize the given address
2500 format, with versionE<nbsp>2.7p4 we had to specify the type explicitly. So
2501 with that version, the following configuration worked for us:
2504 Device "-s localhost:4304"
2507 This directive is B<required> and does not have a default value.
2509 =item B<Sensor> I<Sensor>
2511 Selects sensors to collect or to ignore, depending on B<IgnoreSelected>, see
2512 below. Sensors are specified without the family byte at the beginning, to you'd
2513 use C<F10FCA000800>, and B<not> include the leading C<10.> family byte and
2516 =item B<IgnoreSelected> I<true>|I<false>
2518 If no configuration if given, the B<onewire> plugin will collect data from all
2519 sensors found. This may not be practical, especially if sensors are added and
2520 removed regularly. Sometimes, however, it's easier/preferred to collect only
2521 specific sensors or all sensors I<except> a few specified ones. This option
2522 enables you to do that: By setting B<IgnoreSelected> to I<true> the effect of
2523 B<Sensor> is inverted: All selected interfaces are ignored and all other
2524 interfaces are collected.
2526 =item B<Interval> I<Seconds>
2528 Sets the interval in which all sensors should be read. If not specified, the
2529 global B<Interval> setting is used.
2533 B<EXPERIMENTAL!> The C<onewire> plugin is experimental, because it doesn't yet
2534 work with big setups. It works with one sensor being attached to one
2535 controller, but as soon as you throw in a couple more senors and maybe a hub
2536 or two, reading all values will take more than ten seconds (the default
2537 interval). We will probably add some separate thread for reading the sensors
2538 and some cache or something like that, but it's not done yet. We will try to
2539 maintain backwards compatibility in the future, but we can't promise. So in
2540 short: If it works for you: Great! But keep in mind that the config I<might>
2541 change, though this is unlikely. Oh, and if you want to help improving this
2542 plugin, just send a short notice to the mailing list. ThanksE<nbsp>:)
2544 =head2 Plugin C<openvpn>
2546 The OpenVPN plugin reads a status file maintained by OpenVPN and gathers
2547 traffic statistics about connected clients.
2549 To set up OpenVPN to write to the status file periodically, use the
2550 B<--status> option of OpenVPN. Since OpenVPN can write two different formats,
2551 you need to set the required format, too. This is done by setting
2552 B<--status-version> to B<2>.
2554 So, in a nutshell you need:
2556 openvpn $OTHER_OPTIONS \
2557 --status "/var/run/openvpn-status" 10 \
2564 =item B<StatusFile> I<File>
2566 Specifies the location of the status file.
2570 =head2 Plugin C<oracle>
2572 The "oracle" plugin uses the Oracle® Call Interface I<(OCI)> to connect to an
2573 Oracle® Database and lets you execute SQL statements there. It is very similar
2574 to the "dbi" plugin, because it was written around the same time. See the "dbi"
2575 plugin's documentation above for details.
2578 <Query "out_of_stock">
2579 Statement "SELECT category, COUNT(*) AS value FROM products WHERE in_stock = 0 GROUP BY category"
2582 # InstancePrefix "foo"
2583 InstancesFrom "category"
2587 <Database "product_information">
2591 Query "out_of_stock"
2595 =head3 B<Query> blocks
2597 The Query blocks are handled identically to the Query blocks of the "dbi"
2598 plugin. Please see its documentation above for details on how to specify
2601 =head3 B<Database> blocks
2603 Database blocks define a connection to a database and which queries should be
2604 sent to that database. Each database needs a "name" as string argument in the
2605 starting tag of the block. This name will be used as "PluginInstance" in the
2606 values submitted to the daemon. Other than that, that name is not used.
2610 =item B<ConnectID> I<ID>
2612 Defines the "database alias" or "service name" to connect to. Usually, these
2613 names are defined in the file named C<$ORACLE_HOME/network/admin/tnsnames.ora>.
2615 =item B<Username> I<Username>
2617 Username used for authentication.
2619 =item B<Password> I<Password>
2621 Password used for authentication.
2623 =item B<Query> I<QueryName>
2625 Associates the query named I<QueryName> with this database connection. The
2626 query needs to be defined I<before> this statement, i.E<nbsp>e. all query
2627 blocks you want to refer to must be placed above the database block you want to
2632 =head2 Plugin C<perl>
2634 This plugin embeds a Perl-interpreter into collectd and provides an interface
2635 to collectd's plugin system. See L<collectd-perl(5)> for its documentation.
2637 =head2 Plugin C<ping>
2639 The I<Ping> plugin starts a new thread which sends ICMP "ping" packets to the
2640 configured hosts periodically and measures the network latency. Whenever the
2641 C<read> function of the plugin is called, it submits the average latency, the
2642 standard deviation and the drop rate for each host.
2644 Available configuration options:
2648 =item B<Host> I<IP-address>
2650 Host to ping periodically. This option may be repeated several times to ping
2653 =item B<Interval> I<Seconds>
2655 Sets the interval in which to send ICMP echo packets to the configured hosts.
2656 This is B<not> the interval in which statistics are queries from the plugin but
2657 the interval in which the hosts are "pinged". Therefore, the setting here
2658 should be smaller than or equal to the global B<Interval> setting. Fractional
2659 times, such as "1.24" are allowed.
2663 =item B<Timeout> I<Seconds>
2665 Time to wait for a response from the host to which an ICMP packet had been
2666 sent. If a reply was not received after I<Seconds> seconds, the host is assumed
2667 to be down or the packet to be dropped. This setting must be smaller than the
2668 B<Interval> setting above for the plugin to work correctly. Fractional
2669 arguments are accepted.
2673 =item B<TTL> I<0-255>
2675 Sets the Time-To-Live of generated ICMP packets.
2679 =head2 Plugin C<postgresql>
2681 The C<postgresql> plugin queries statistics from PostgreSQL databases. It
2682 keeps a persistent connection to all configured databases and tries to
2683 reconnect if the connection has been interrupted. A database is configured by
2684 specifying a B<Database> block as described below. The default statistics are
2685 collected from PostgreSQL's B<statistics collector> which thus has to be
2686 enabled for this plugin to work correctly. This should usually be the case by
2687 default. See the section "The Statistics Collector" of the B<PostgreSQL
2688 Documentation> for details.
2690 By specifying custom database queries using a B<Query> block as described
2691 below, you may collect any data that is available from some PostgreSQL
2692 database. This way, you are able to access statistics of external daemons
2693 which are available in a PostgreSQL database or use future or special
2694 statistics provided by PostgreSQL without the need to upgrade your collectd
2697 The B<PostgreSQL Documentation> manual can be found at
2698 L<http://www.postgresql.org/docs/manuals/>.
2702 Statement "SELECT magic FROM wizard WHERE host = $1;"
2706 InstancePrefix "magic"
2711 <Query rt36_tickets>
2712 Statement "SELECT COUNT(type) AS count, type \
2714 WHEN resolved = 'epoch' THEN 'open' \
2715 ELSE 'resolved' END AS type \
2716 FROM tickets) type \
2720 InstancePrefix "rt36_tickets"
2721 InstancesFrom "type"
2732 KRBSrvName "kerberos_service_name"
2737 Service "service_name"
2738 Query backend # predefined
2743 The B<Query> block defines one database query which may later be used by a
2744 database definition. It accepts a single mandatory argument which specifies
2745 the name of the query. The names of all queries have to be unique (see the
2746 B<MinVersion> and B<MaxVersion> options below for an exception to this
2747 rule). The following configuration options are available to define the query:
2749 In each B<Query> block, there is one or more B<Result> blocks. B<Result>
2750 blocks define how to handle the values returned from the query. They define
2751 which column holds which value and how to dispatch that value to the daemon.
2752 Multiple B<Result> blocks may be used to extract multiple values from a single
2757 =item B<Statement> I<sql query statement>
2759 Specify the I<sql query statement> which the plugin should execute. The string
2760 may contain the tokens B<$1>, B<$2>, etc. which are used to reference the
2761 first, second, etc. parameter. The value of the parameters is specified by the
2762 B<Param> configuration option - see below for details. To include a literal
2763 B<$> character followed by a number, surround it with single quotes (B<'>).
2765 Any SQL command which may return data (such as C<SELECT> or C<SHOW>) is
2766 allowed. Note, however, that only a single command may be used. Semicolons are
2767 allowed as long as a single non-empty command has been specified only.
2769 The returned lines will be handled separately one after another.
2771 =item B<Query> I<sql query statement>
2773 This is a deprecated synonym for B<Statement>. It will be removed in version 5
2776 =item B<Param> I<hostname>|I<database>|I<username>|I<interval>
2778 Specify the parameters which should be passed to the SQL query. The parameters
2779 are referred to in the SQL query as B<$1>, B<$2>, etc. in the same order as
2780 they appear in the configuration file. The value of the parameter is
2781 determined depending on the value of the B<Param> option as follows:
2787 The configured hostname of the database connection. If a UNIX domain socket is
2788 used, the parameter expands to "localhost".
2792 The name of the database of the current connection.
2796 The username used to connect to the database.
2800 The interval collectd is using (as specified by the B<Interval> option).
2804 Please note that parameters are only supported by PostgreSQL's protocol
2805 version 3 and above which was introduced in version 7.4 of PostgreSQL.
2807 =item B<Type> I<type>
2809 The I<type> name to be used when dispatching the values. The type describes
2810 how to handle the data and where to store it. See L<types.db(5)> for more
2811 details on types and their configuration. The number and type of values (as
2812 selected by the B<ValuesFrom> option) has to match the type of the given name.
2814 This option is required inside a B<Result> block.
2816 =item B<InstancePrefix> I<prefix>
2818 =item B<InstancesFrom> I<column0> [I<column1> ...]
2820 Specify how to create the "TypeInstance" for each data set (i.E<nbsp>e. line).
2821 B<InstancePrefix> defines a static prefix that will be prepended to all type
2822 instances. B<InstancesFrom> defines the column names whose values will be used
2823 to create the type instance. Multiple values will be joined together using the
2824 hyphen (C<->) as separation character.
2826 The plugin itself does not check whether or not all built instances are
2827 different. It is your responsibility to assure that each is unique.
2829 Both options are optional. If none is specified, the type instance will be
2832 =item B<ValuesFrom> I<column0> [I<column1> ...]
2834 Names the columns whose content is used as the actual data for the data sets
2835 that are dispatched to the daemon. How many such columns you need is
2836 determined by the B<Type> setting as explained above. If you specify too many
2837 or not enough columns, the plugin will complain about that and no data will be
2838 submitted to the daemon.
2840 The actual data type, as seen by PostgreSQL, is not that important as long as
2841 it represents numbers. The plugin will automatically cast the values to the
2842 right type if it know how to do that. For that, it uses the L<strtoll(3)> and
2843 L<strtod(3)> functions, so anything supported by those functions is supported
2844 by the plugin as well.
2846 This option is required inside a B<Result> block and may be specified multiple
2847 times. If multiple B<ValuesFrom> options are specified, the columns are read
2850 =item B<Column> I<type> [I<type instance>]
2852 This is a deprecated alternative to a B<Result> block. It will be removed in
2853 version 5 of collectd. It is equivalent to the following B<Result> block:
2857 InstancePrefix I<type instance>
2858 ValuesFrom I<name of the x. column>
2861 The order of the B<Column> options defines which columns of the query result
2862 should be used. The first option specifies the data found in the first column,
2863 the second option that of the second column, and so on.
2865 =item B<MinVersion> I<version>
2867 =item B<MaxVersion> I<version>
2869 Specify the minimum or maximum version of PostgreSQL that this query should be
2870 used with. Some statistics might only be available with certain versions of
2871 PostgreSQL. This allows you to specify multiple queries with the same name but
2872 which apply to different versions, thus allowing you to use the same
2873 configuration in a heterogeneous environment.
2875 The I<version> has to be specified as the concatenation of the major, minor
2876 and patch-level versions, each represented as two-decimal-digit numbers. For
2877 example, version 8.2.3 will become 80203.
2879 =item B<MinPGVersion> I<version>
2881 =item B<MaxPGVersion> I<version>
2883 These are deprecated synonyms for B<MinVersion> and B<MaxVersion>
2884 respectively. They will be removed in version 5 of collectd.
2888 The following predefined queries are available (the definitions can be found
2889 in the F<postgresql_default.conf> file which, by default, is available at
2890 C<I<prefix>/share/collectd/>):
2896 This query collects the number of backends, i.E<nbsp>e. the number of
2899 =item B<transactions>
2901 This query collects the numbers of committed and rolled-back transactions of
2906 This query collects the numbers of various table modifications (i.E<nbsp>e.
2907 insertions, updates, deletions) of the user tables.
2909 =item B<query_plans>
2911 This query collects the numbers of various table scans and returned tuples of
2914 =item B<table_states>
2916 This query collects the numbers of live and dead rows in the user tables.
2920 This query collects disk block access counts for user tables.
2924 This query collects the on-disk size of the database in bytes.
2928 The B<Database> block defines one PostgreSQL database for which to collect
2929 statistics. It accepts a single mandatory argument which specifies the
2930 database name. None of the other options are required. PostgreSQL will use
2931 default values as documented in the section "CONNECTING TO A DATABASE" in the
2932 L<psql(1)> manpage. However, be aware that those defaults may be influenced by
2933 the user collectd is run as and special environment variables. See the manpage
2938 =item B<Host> I<hostname>
2940 Specify the hostname or IP of the PostgreSQL server to connect to. If the
2941 value begins with a slash, it is interpreted as the directory name in which to
2942 look for the UNIX domain socket.
2944 This option is also used to determine the hostname that is associated with a
2945 collected data set. If it has been omitted or either begins with with a slash
2946 or equals B<localhost> it will be replaced with the global hostname definition
2947 of collectd. Any other value will be passed literally to collectd when
2948 dispatching values. Also see the global B<Hostname> and B<FQDNLookup> options.
2950 =item B<Port> I<port>
2952 Specify the TCP port or the local UNIX domain socket file extension of the
2955 =item B<User> I<username>
2957 Specify the username to be used when connecting to the server.
2959 =item B<Password> I<password>
2961 Specify the password to be used when connecting to the server.
2963 =item B<SSLMode> I<disable>|I<allow>|I<prefer>|I<require>
2965 Specify whether to use an SSL connection when contacting the server. The
2966 following modes are supported:
2972 Do not use SSL at all.
2976 First, try to connect without using SSL. If that fails, try using SSL.
2978 =item I<prefer> (default)
2980 First, try to connect using SSL. If that fails, try without using SSL.
2988 =item B<KRBSrvName> I<kerberos_service_name>
2990 Specify the Kerberos service name to use when authenticating with Kerberos 5
2991 or GSSAPI. See the sections "Kerberos authentication" and "GSSAPI" of the
2992 B<PostgreSQL Documentation> for details.
2994 =item B<Service> I<service_name>
2996 Specify the PostgreSQL service name to use for additional parameters. That
2997 service has to be defined in F<pg_service.conf> and holds additional
2998 connection parameters. See the section "The Connection Service File" in the
2999 B<PostgreSQL Documentation> for details.
3001 =item B<Query> I<query>
3003 Specify a I<query> which should be executed for the database connection. This
3004 may be any of the predefined or user-defined queries. If no such option is
3005 given, it defaults to "backends", "transactions", "queries", "query_plans",
3006 "table_states", "disk_io" and "disk_usage". Else, the specified queries are
3011 =head2 Plugin C<powerdns>
3013 The C<powerdns> plugin queries statistics from an authoritative PowerDNS
3014 nameserver and/or a PowerDNS recursor. Since both offer a wide variety of
3015 values, many of which are probably meaningless to most users, but may be useful
3016 for some. So you may chose which values to collect, but if you don't, some
3017 reasonable defaults will be collected.
3020 <Server "server_name">
3022 Collect "udp-answers" "udp-queries"
3023 Socket "/var/run/pdns.controlsocket"
3025 <Recursor "recursor_name">
3027 Collect "cache-hits" "cache-misses"
3028 Socket "/var/run/pdns_recursor.controlsocket"
3030 LocalSocket "/opt/collectd/var/run/collectd-powerdns"
3035 =item B<Server> and B<Recursor> block
3037 The B<Server> block defines one authoritative server to query, the B<Recursor>
3038 does the same for an recursing server. The possible options in both blocks are
3039 the same, though. The argument defines a name for the serverE<nbsp>/ recursor
3044 =item B<Collect> I<Field>
3046 Using the B<Collect> statement you can select which values to collect. Here,
3047 you specify the name of the values as used by the PowerDNS servers, e.E<nbsp>g.
3048 C<dlg-only-drops>, C<answers10-100>.
3050 The method of getting the values differs for B<Server> and B<Recursor> blocks:
3051 When querying the server a C<SHOW *> command is issued in any case, because
3052 that's the only way of getting multiple values out of the server at once.
3053 collectd then picks out the values you have selected. When querying the
3054 recursor, a command is generated to query exactly these values. So if you
3055 specify invalid fields when querying the recursor, a syntax error may be
3056 returned by the daemon and collectd may not collect any values at all.
3058 If no B<Collect> statement is given, the following B<Server> values will be
3065 =item packetcache-hit
3067 =item packetcache-miss
3069 =item packetcache-size
3071 =item query-cache-hit
3073 =item query-cache-miss
3075 =item recursing-answers
3077 =item recursing-questions
3089 The following B<Recursor> values will be collected by default:
3093 =item noerror-answers
3095 =item nxdomain-answers
3097 =item servfail-answers
3115 Please note that up to that point collectd doesn't know what values are
3116 available on the server and values that are added do not need a change of the
3117 mechanism so far. However, the values must be mapped to collectd's naming
3118 scheme, which is done using a lookup table that lists all known values. If
3119 values are added in the future and collectd does not know about them, you will
3120 get an error much like this:
3122 powerdns plugin: submit: Not found in lookup table: foobar = 42
3124 In this case please file a bug report with the collectd team.
3126 =item B<Socket> I<Path>
3128 Configures the path to the UNIX domain socket to be used when connecting to the
3129 daemon. By default C<${localstatedir}/run/pdns.controlsocket> will be used for
3130 an authoritative server and C<${localstatedir}/run/pdns_recursor.controlsocket>
3131 will be used for the recursor.
3135 =item B<LocalSocket> I<Path>
3137 Querying the recursor is done using UDP. When using UDP over UNIX domain
3138 sockets, the client socket needs a name in the file system, too. You can set
3139 this local name to I<Path> using the B<LocalSocket> option. The default is
3140 C<I<prefix>/var/run/collectd-powerdns>.
3144 =head2 Plugin C<processes>
3148 =item B<Process> I<Name>
3150 Select more detailed statistics of processes matching this name. The statistics
3151 collected for these selected processes are size of the resident segment size
3152 (RSS), user- and system-time used, number of processes and number of threads,
3153 and minor and major pagefaults.
3155 =item B<ProcessMatch> I<name> I<regex>
3157 Similar to the B<Process> option this allows to select more detailed
3158 statistics of processes matching the specified I<regex> (see L<regex(7)> for
3159 details). The statistics of all matching processes are summed up and
3160 dispatched to the daemon using the specified I<name> as an identifier. This
3161 allows to "group" several processes together. I<name> must not contain
3166 =head2 Plugin C<protocols>
3168 Collects a lot of information about various network protocols, such as I<IP>,
3169 I<TCP>, I<UDP>, etc.
3171 Available configuration options:
3175 =item B<Value> I<Selector>
3177 Selects whether or not to select a specific value. The string being matched is
3178 of the form "I<Protocol>:I<ValueName>", where I<Protocol> will be used as the
3179 plugin instance and I<ValueName> will be used as type instance. An example of
3180 the string being used would be C<Tcp:RetransSegs>.
3182 You can use regular expressions to match a large number of values with just one
3183 configuration option. To select all "extended" I<TCP> values, you could use the
3184 following statement:
3188 Whether only matched values are selected or all matched values are ignored
3189 depends on the B<IgnoreSelected>. By default, only matched values are selected.
3190 If no value is configured at all, all values will be selected.
3192 =item B<IgnoreSelected> B<true>|B<false>
3194 If set to B<true>, inverts the selection made by B<Value>, i.E<nbsp>e. all
3195 matching values will be ignored.
3199 =head2 Plugin C<rrdcached>
3201 The C<rrdcached> plugin uses the RRDtool accelerator daemon, L<rrdcached(1)>,
3202 to store values to RRD files in an efficient manner. The combination of the
3203 C<rrdcached> B<plugin> and the C<rrdcached> B<daemon> is very similar to the
3204 way the C<rrdtool> plugin works (see below). The added abstraction layer
3205 provides a number of benefits, though: Because the cache is not within
3206 C<collectd> anymore, it does not need to be flushed when C<collectd> is to be
3207 restarted. This results in much shorter (if any) gaps in graphs, especially
3208 under heavy load. Also, the C<rrdtool> command line utility is aware of the
3209 daemon so that it can flush values to disk automatically when needed. This
3210 allows to integrate automated flushing of values into graphing solutions much
3213 There are disadvantages, though: The daemon may reside on a different host, so
3214 it may not be possible for C<collectd> to create the appropriate RRD files
3215 anymore. And even if C<rrdcached> runs on the same host, it may run in a
3216 different base directory, so relative paths may do weird stuff if you're not
3219 So the B<recommended configuration> is to let C<collectd> and C<rrdcached> run
3220 on the same host, communicating via a UNIX domain socket. The B<DataDir>
3221 setting should be set to an absolute path, so that a changed base directory
3222 does not result in RRD files being createdE<nbsp>/ expected in the wrong place.
3226 =item B<DaemonAddress> I<Address>
3228 Address of the daemon as understood by the C<rrdc_connect> function of the RRD
3229 library. See L<rrdcached(1)> for details. Example:
3231 <Plugin "rrdcached">
3232 DaemonAddress "unix:/var/run/rrdcached.sock"
3235 =item B<DataDir> I<Directory>
3237 Set the base directory in which the RRD files reside. If this is a relative
3238 path, it is relative to the working base directory of the C<rrdcached> daemon!
3239 Use of an absolute path is recommended.
3241 =item B<CreateFiles> B<true>|B<false>
3243 Enables or disables the creation of RRD files. If the daemon is not running
3244 locally, or B<DataDir> is set to a relative path, this will not work as
3245 expected. Default is B<true>.
3249 =head2 Plugin C<rrdtool>
3251 You can use the settings B<StepSize>, B<HeartBeat>, B<RRARows>, and B<XFF> to
3252 fine-tune your RRD-files. Please read L<rrdcreate(1)> if you encounter problems
3253 using these settings. If you don't want to dive into the depths of RRDtool, you
3254 can safely ignore these settings.
3258 =item B<DataDir> I<Directory>
3260 Set the directory to store RRD-files under. Per default RRD-files are generated
3261 beneath the daemon's working directory, i.E<nbsp>e. the B<BaseDir>.
3263 =item B<StepSize> I<Seconds>
3265 B<Force> the stepsize of newly created RRD-files. Ideally (and per default)
3266 this setting is unset and the stepsize is set to the interval in which the data
3267 is collected. Do not use this option unless you absolutely have to for some
3268 reason. Setting this option may cause problems with the C<snmp plugin>, the
3269 C<exec plugin> or when the daemon is set up to receive data from other hosts.
3271 =item B<HeartBeat> I<Seconds>
3273 B<Force> the heartbeat of newly created RRD-files. This setting should be unset
3274 in which case the heartbeat is set to twice the B<StepSize> which should equal
3275 the interval in which data is collected. Do not set this option unless you have
3276 a very good reason to do so.
3278 =item B<RRARows> I<NumRows>
3280 The C<rrdtool plugin> calculates the number of PDPs per CDP based on the
3281 B<StepSize>, this setting and a timespan. This plugin creates RRD-files with
3282 three times five RRAs, i. e. five RRAs with the CFs B<MIN>, B<AVERAGE>, and
3283 B<MAX>. The five RRAs are optimized for graphs covering one hour, one day, one
3284 week, one month, and one year.
3286 So for each timespan, it calculates how many PDPs need to be consolidated into
3287 one CDP by calculating:
3288 number of PDPs = timespan / (stepsize * rrarows)
3290 Bottom line is, set this no smaller than the width of you graphs in pixels. The
3293 =item B<RRATimespan> I<Seconds>
3295 Adds an RRA-timespan, given in seconds. Use this option multiple times to have
3296 more then one RRA. If this option is never used, the built-in default of (3600,
3297 86400, 604800, 2678400, 31622400) is used.
3299 For more information on how RRA-sizes are calculated see B<RRARows> above.
3301 =item B<XFF> I<Factor>
3303 Set the "XFiles Factor". The default is 0.1. If unsure, don't set this option.
3305 =item B<CacheFlush> I<Seconds>
3307 When the C<rrdtool> plugin uses a cache (by setting B<CacheTimeout>, see below)
3308 it writes all values for a certain RRD-file if the oldest value is older than
3309 (or equal to) the number of seconds specified. If some RRD-file is not updated
3310 anymore for some reason (the computer was shut down, the network is broken,
3311 etc.) some values may still be in the cache. If B<CacheFlush> is set, then the
3312 entire cache is searched for entries older than B<CacheTimeout> seconds and
3313 written to disk every I<Seconds> seconds. Since this is kind of expensive and
3314 does nothing under normal circumstances, this value should not be too small.
3315 900 seconds might be a good value, though setting this to 7200 seconds doesn't
3316 normally do much harm either.
3318 =item B<CacheTimeout> I<Seconds>
3320 If this option is set to a value greater than zero, the C<rrdtool plugin> will
3321 save values in a cache, as described above. Writing multiple values at once
3322 reduces IO-operations and thus lessens the load produced by updating the files.
3323 The trade off is that the graphs kind of "drag behind" and that more memory is
3326 =item B<WritesPerSecond> I<Updates>
3328 When collecting many statistics with collectd and the C<rrdtool> plugin, you
3329 will run serious performance problems. The B<CacheFlush> setting and the
3330 internal update queue assert that collectd continues to work just fine even
3331 under heavy load, but the system may become very unresponsive and slow. This is
3332 a problem especially if you create graphs from the RRD files on the same
3333 machine, for example using the C<graph.cgi> script included in the
3334 C<contrib/collection3/> directory.
3336 This setting is designed for very large setups. Setting this option to a value
3337 between 25 and 80 updates per second, depending on your hardware, will leave
3338 the server responsive enough to draw graphs even while all the cached values
3339 are written to disk. Flushed values, i.E<nbsp>e. values that are forced to disk
3340 by the B<FLUSH> command, are B<not> effected by this limit. They are still
3341 written as fast as possible, so that web frontends have up to date data when
3344 For example: If you have 100,000 RRD files and set B<WritesPerSecond> to 30
3345 updates per second, writing all values to disk will take approximately
3346 56E<nbsp>minutes. Together with the flushing ability that's integrated into
3347 "collection3" you'll end up with a responsive and fast system, up to date
3348 graphs and basically a "backup" of your values every hour.
3350 =item B<RandomTimeout> I<Seconds>
3352 When set, the actual timeout for each value is chosen randomly between
3353 I<CacheTimeout>-I<RandomTimeout> and I<CacheTimeout>+I<RandomTimeout>. The
3354 intention is to avoid high load situations that appear when many values timeout
3355 at the same time. This is especially a problem shortly after the daemon starts,
3356 because all values were added to the internal cache at roughly the same time.
3360 =head2 Plugin C<sensors>
3362 The C<sensors plugin> uses B<lm_sensors> to retrieve sensor-values. This means
3363 that all the needed modules have to be loaded and lm_sensors has to be
3364 configured (most likely by editing F</etc/sensors.conf>. Read
3365 L<sensors.conf(5)> for details.
3367 The B<lm_sensors> homepage can be found at
3368 L<http://secure.netroedge.com/~lm78/>.
3372 =item B<Sensor> I<chip-bus-address/type-feature>
3374 Selects the name of the sensor which you want to collect or ignore, depending
3375 on the B<IgnoreSelected> below. For example, the option "B<Sensor>
3376 I<it8712-isa-0290/voltage-in1>" will cause collectd to gather data for the
3377 voltage sensor I<in1> of the I<it8712> on the isa bus at the address 0290.
3379 =item B<IgnoreSelected> I<true>|I<false>
3381 If no configuration if given, the B<sensors>-plugin will collect data from all
3382 sensors. This may not be practical, especially for uninteresting sensors.
3383 Thus, you can use the B<Sensor>-option to pick the sensors you're interested
3384 in. Sometimes, however, it's easier/preferred to collect all sensors I<except> a
3385 few ones. This option enables you to do that: By setting B<IgnoreSelected> to
3386 I<true> the effect of B<Sensor> is inverted: All selected sensors are ignored
3387 and all other sensors are collected.
3391 =head2 Plugin C<snmp>
3393 Since the configuration of the C<snmp plugin> is a little more complicated than
3394 other plugins, its documentation has been moved to an own manpage,
3395 L<collectd-snmp(5)>. Please see there for details.
3397 =head2 Plugin C<syslog>
3401 =item B<LogLevel> B<debug|info|notice|warning|err>
3403 Sets the log-level. If, for example, set to B<notice>, then all events with
3404 severity B<notice>, B<warning>, or B<err> will be submitted to the
3407 Please note that B<debug> is only available if collectd has been compiled with
3412 =head2 Plugin C<table>
3414 The C<table plugin> provides generic means to parse tabular data and dispatch
3415 user specified values. Values are selected based on column numbers. For
3416 example, this plugin may be used to get values from the Linux L<proc(5)>
3417 filesystem or CSV (comma separated values) files.
3420 <Table "/proc/slabinfo">
3425 InstancePrefix "active_objs"
3431 InstancePrefix "objperslab"
3438 The configuration consists of one or more B<Table> blocks, each of which
3439 configures one file to parse. Within each B<Table> block, there are one or
3440 more B<Result> blocks, which configure which data to select and how to
3443 The following options are available inside a B<Table> block:
3447 =item B<Instance> I<instance>
3449 If specified, I<instance> is used as the plugin instance. So, in the above
3450 example, the plugin name C<table-slabinfo> would be used. If omitted, the
3451 filename of the table is used instead, with all special characters replaced
3452 with an underscore (C<_>).
3454 =item B<Separator> I<string>
3456 Any character of I<string> is interpreted as a delimiter between the different
3457 columns of the table. A sequence of two or more contiguous delimiters in the
3458 table is considered to be a single delimiter, i.E<nbsp>e. there cannot be any
3459 empty columns. The plugin uses the L<strtok_r(3)> function to parse the lines
3460 of a table - see its documentation for more details. This option is mandatory.
3462 A horizontal tab, newline and carriage return may be specified by C<\\t>,
3463 C<\\n> and C<\\r> respectively. Please note that the double backslashes are
3464 required because of collectd's config parsing.
3468 The following options are available inside a B<Result> block:
3472 =item B<Type> I<type>
3474 Sets the type used to dispatch the values to the daemon. Detailed information
3475 about types and their configuration can be found in L<types.db(5)>. This
3476 option is mandatory.
3478 =item B<InstancePrefix> I<prefix>
3480 If specified, prepend I<prefix> to the type instance. If omitted, only the
3481 B<InstancesFrom> option is considered for the type instance.
3483 =item B<InstancesFrom> I<column0> [I<column1> ...]
3485 If specified, the content of the given columns (identified by the column
3486 number starting at zero) will be used to create the type instance for each
3487 row. Multiple values (and the instance prefix) will be joined together with
3488 dashes (I<->) as separation character. If omitted, only the B<InstancePrefix>
3489 option is considered for the type instance.
3491 The plugin itself does not check whether or not all built instances are
3492 different. It’s your responsibility to assure that each is unique. This is
3493 especially true, if you do not specify B<InstancesFrom>: B<You> have to make
3494 sure that the table only contains one row.
3496 If neither B<InstancePrefix> nor B<InstancesFrom> is given, the type instance
3499 =item B<ValuesFrom> I<column0> [I<column1> ...]
3501 Specifies the columns (identified by the column numbers starting at zero)
3502 whose content is used as the actual data for the data sets that are dispatched
3503 to the daemon. How many such columns you need is determined by the B<Type>
3504 setting above. If you specify too many or not enough columns, the plugin will
3505 complain about that and no data will be submitted to the daemon. The plugin
3506 uses L<strtoll(3)> and L<strtod(3)> to parse counter and gauge values
3507 respectively, so anything supported by those functions is supported by the
3508 plugin as well. This option is mandatory.
3512 =head2 Plugin C<tail>
3514 The C<tail plugin> follows logfiles, just like L<tail(1)> does, parses
3515 each line and dispatches found values. What is matched can be configured by the
3516 user using (extended) regular expressions, as described in L<regex(7)>.
3519 <File "/var/log/exim4/mainlog">
3522 Regex "S=([1-9][0-9]*)"
3528 Regex "\\<R=local_user\\>"
3531 Instance "local_user"
3536 The config consists of one or more B<File> blocks, each of which configures one
3537 logfile to parse. Within each B<File> block, there are one or more B<Match>
3538 blocks, which configure a regular expression to search for.
3540 The B<Instance> option in the B<File> block may be used to set the plugin
3541 instance. So in the above example the plugin name C<tail-foo> would be used.
3542 This plugin instance is for all B<Match> blocks that B<follow> it, until the
3543 next B<Instance> option. This way you can extract several plugin instances from
3544 one logfile, handy when parsing syslog and the like.
3546 Each B<Match> block has the following options to describe how the match should
3551 =item B<Regex> I<regex>
3553 Sets the regular expression to use for matching against a line. The first
3554 subexpression has to match something that can be turned into a number by
3555 L<strtoll(3)> or L<strtod(3)>, depending on the value of C<CounterAdd>, see
3556 below. Because B<extended> regular expressions are used, you do not need to use
3557 backslashes for subexpressions! If in doubt, please consult L<regex(7)>. Due to
3558 collectd's config parsing you need to escape backslashes, though. So if you
3559 want to match literal parentheses you need to do the following:
3561 Regex "SPAM \\(Score: (-?[0-9]+\\.[0-9]+)\\)"
3563 =item B<DSType> I<Type>
3565 Sets how the values are cumulated. I<Type> is one of:
3569 =item B<GaugeAverage>
3571 Calculate the average.
3575 Use the smallest number only.
3579 Use the greatest number only.
3583 Use the last number found.
3587 The matched number is a counter. Simply sets the internal counter to this
3592 Add the matched value to the internal counter.
3596 Increase the internal counter by one. This B<DSType> is the only one that does
3597 not use the matched subexpression, but simply counts the number of matched
3598 lines. Thus, you may use a regular expression without submatch in this case.
3602 As you'd expect the B<Gauge*> types interpret the submatch as a floating point
3603 number, using L<strtod(3)>. The B<CounterSet> and B<CounterAdd> interpret the
3604 submatch as an integer using L<strtoll(3)>. B<CounterInc> does not use the
3605 submatch at all and it may be omitted in this case.
3607 =item B<Type> I<Type>
3609 Sets the type used to dispatch this value. Detailed information about types and
3610 their configuration can be found in L<types.db(5)>.
3612 =item B<Instance> I<TypeInstance>
3614 This optional setting sets the type instance to use.
3618 =head2 Plugin C<teamspeak2>
3620 The C<teamspeak2 plugin> connects to the query port of a teamspeak2 server and
3621 polls interesting global and virtual server data. The plugin can query only one
3622 physical server but unlimited virtual servers. You can use the following
3623 options to configure it:
3627 =item B<Host> I<hostname/ip>
3629 The hostname or ip which identifies the physical server.
3632 =item B<Port> I<port>
3634 The query port of the physical server. This needs to be a string.
3637 =item B<Server> I<port>
3639 This option has to be added once for every virtual server the plugin should
3640 query. If you want to query the virtual server on port 8767 this is what the
3641 option would look like:
3645 This option, although numeric, needs to be a string, i.E<nbsp>e. you B<must>
3646 use quotes around it! If no such statement is given only global information
3651 =head2 Plugin C<ted>
3653 The I<TED> plugin connects to a device of "The Energy Detective", a device to
3654 measure power consumption. These devices are usually connected to a serial
3655 (RS232) or USB port. The plugin opens a configured device and tries to read the
3656 current energy readings. For more information on TED, visit
3657 L<http://www.theenergydetective.com/>.
3659 Available configuration options:
3663 =item B<Device> I<Path>
3665 Path to the device on which TED is connected. collectd will need read and write
3666 permissions on that file.
3668 Default: B</dev/ttyUSB0>
3670 =item B<Retries> I<Num>
3672 Apparently reading from TED is not that reliable. You can therefore configure a
3673 number of retries here. You only configure the I<retries> here, to if you
3674 specify zero, one reading will be performed (but no retries if that fails); if
3675 you specify three, a maximum of four readings are performed. Negative values
3682 =head2 Plugin C<tcpconns>
3684 The C<tcpconns plugin> counts the number of currently established TCP
3685 connections based on the local port and/or the remote port. Since there may be
3686 a lot of connections the default if to count all connections with a local port,
3687 for which a listening socket is opened. You can use the following options to
3688 fine-tune the ports you are interested in:
3692 =item B<ListeningPorts> I<true>|I<false>
3694 If this option is set to I<true>, statistics for all local ports for which a
3695 listening socket exists are collected. The default depends on B<LocalPort> and
3696 B<RemotePort> (see below): If no port at all is specifically selected, the
3697 default is to collect listening ports. If specific ports (no matter if local or
3698 remote ports) are selected, this option defaults to I<false>, i.E<nbsp>e. only
3699 the selected ports will be collected unless this option is set to I<true>
3702 =item B<LocalPort> I<Port>
3704 Count the connections to a specific local port. This can be used to see how
3705 many connections are handled by a specific daemon, e.E<nbsp>g. the mailserver.
3706 You have to specify the port in numeric form, so for the mailserver example
3707 you'd need to set B<25>.
3709 =item B<RemotePort> I<Port>
3711 Count the connections to a specific remote port. This is useful to see how
3712 much a remote service is used. This is most useful if you want to know how many
3713 connections a local service has opened to remote services, e.E<nbsp>g. how many
3714 connections a mail server or news server has to other mail or news servers, or
3715 how many connections a web proxy holds to web servers. You have to give the
3716 port in numeric form.
3720 =head2 Plugin C<thermal>
3724 =item B<ForceUseProcfs> I<true>|I<false>
3726 By default, the C<thermal> plugin tries to read the statistics from the Linux
3727 C<sysfs> interface. If that is not available, the plugin falls back to the
3728 C<procfs> interface. By setting this option to I<true>, you can force the
3729 plugin to use the latter. This option defaults to I<false>.
3731 =item B<Device> I<Device>
3733 Selects the name of the thermal device that you want to collect or ignore,
3734 depending on the value of the B<IgnoreSelected> option. This option may be
3735 used multiple times to specify a list of devices.
3737 =item B<IgnoreSelected> I<true>|I<false>
3739 Invert the selection: If set to true, all devices B<except> the ones that
3740 match the device names specified by the B<Device> option are collected. By
3741 default only selected devices are collected if a selection is made. If no
3742 selection is configured at all, B<all> devices are selected.
3746 =head2 Plugin C<tokyotyrant>
3748 The C<tokyotyrant plugin> connects to a TokyoTyrant server and collects a
3749 couple metrics: number of records, and database size on disk.
3753 =item B<Host> I<Hostname/IP>
3755 The hostname or ip which identifies the server.
3756 Default: B<127.0.0.1>
3758 =item B<Port> I<Service/Port>
3760 The query port of the server. This needs to be a string, even if the port is
3761 given in its numeric form.
3766 =head2 Plugin C<unixsock>
3770 =item B<SocketFile> I<Path>
3772 Sets the socket-file which is to be created.
3774 =item B<SocketGroup> I<Group>
3776 If running as root change the group of the UNIX-socket after it has been
3777 created. Defaults to B<collectd>.
3779 =item B<SocketPerms> I<Permissions>
3781 Change the file permissions of the UNIX-socket after it has been created. The
3782 permissions must be given as a numeric, octal value as you would pass to
3783 L<chmod(1)>. Defaults to B<0770>.
3787 =head2 Plugin C<uuid>
3789 This plugin, if loaded, causes the Hostname to be taken from the machine's
3790 UUID. The UUID is a universally unique designation for the machine, usually
3791 taken from the machine's BIOS. This is most useful if the machine is running in
3792 a virtual environment such as Xen, in which case the UUID is preserved across
3793 shutdowns and migration.
3795 The following methods are used to find the machine's UUID, in order:
3801 Check I</etc/uuid> (or I<UUIDFile>).
3805 Check for UUID from HAL (L<http://www.freedesktop.org/wiki/Software/hal>) if
3810 Check for UUID from C<dmidecode> / SMBIOS.
3814 Check for UUID from Xen hypervisor.
3818 If no UUID can be found then the hostname is not modified.
3822 =item B<UUIDFile> I<Path>
3824 Take the UUID from the given file (default I</etc/uuid>).
3828 =head2 Plugin C<vmem>
3830 The C<vmem> plugin collects information about the usage of virtual memory.
3831 Since the statistics provided by the Linux kernel are very detailed, they are
3832 collected very detailed. However, to get all the details, you have to switch
3833 them on manually. Most people just want an overview over, such as the number of
3834 pages read from swap space.
3838 =item B<Verbose> B<true>|B<false>
3840 Enables verbose collection of information. This will start collecting page
3841 "actions", e.E<nbsp>g. page allocations, (de)activations, steals and so on.
3842 Part of these statistics are collected on a "per zone" basis.
3846 =head2 Plugin C<vserver>
3848 This plugin doesn't have any options. B<VServer> support is only available for
3849 Linux. It cannot yet be found in a vanilla kernel, though. To make use of this
3850 plugin you need a kernel that has B<VServer> support built in, i.E<nbsp>e. you
3851 need to apply the patches and compile your own kernel, which will then provide
3852 the F</proc/virtual> filesystem that is required by this plugin.
3854 The B<VServer> homepage can be found at L<http://linux-vserver.org/>.
3856 B<Note>: The traffic collected by this plugin accounts for the amount of
3857 traffic passing a socket which might be a lot less than the actual on-wire
3858 traffic (e.E<nbsp>g. due to headers and retransmission). If you want to
3859 collect on-wire traffic you could, for example, use the logging facilities of
3860 iptables to feed data for the guest IPs into the iptables plugin.
3862 =head2 Plugin C<write_http>
3864 This output plugin submits values to an http server by POST them using the
3865 PUTVAL plain-text protocol. Each destination you want to post data to needs to
3866 have one B<URL> block, within which the destination can be configured further,
3867 for example by specifying authentication data.
3871 <Plugin "write_http">
3872 <URL "http://example.com/post-collectd">
3878 B<URL> blocks need one string argument which is used as the URL to which data
3879 is posted. The following options are understood within B<URL> blocks.
3883 =item B<User> I<Username>
3885 Optional user name needed for authentication.
3887 =item B<Password> I<Password>
3889 Optional password needed for authentication.
3891 =item B<VerifyPeer> B<true>|B<false>
3893 Enable or disable peer SSL certificate verification. See
3894 L<http://curl.haxx.se/docs/sslcerts.html> for details. Enabled by default.
3896 =item B<VerifyHost> B<true|false>
3898 Enable or disable peer host name verification. If enabled, the plugin checks if
3899 the C<Common Name> or a C<Subject Alternate Name> field of the SSL certificate
3900 matches the host name provided by the B<URL> option. If this identity check
3901 fails, the connection is aborted. Obviously, only works when connecting to a
3902 SSL enabled server. Enabled by default.
3904 =item B<CACert> I<File>
3906 File that holds one or more SSL certificates. If you want to use HTTPS you will
3907 possibly need this option. What CA certificates come bundled with C<libcurl>
3908 and are checked by default depends on the distribution you use.
3910 =item B<Format> B<Command>|B<JSON>
3912 Format of the output to generate. If set to B<Command>, will create output that
3913 is understood by the I<Exec> and I<UnixSock> plugins. When set to B<JSON>, will
3914 create output in the I<JavaScript Object Notation> (JSON).
3916 Defaults to B<Command>.
3920 =head1 THRESHOLD CONFIGURATION
3922 Starting with version C<4.3.0> collectd has support for B<monitoring>. By that
3923 we mean that the values are not only stored or sent somewhere, but that they
3924 are judged and, if a problem is recognized, acted upon. The only action
3925 collectd takes itself is to generate and dispatch a "notification". Plugins can
3926 register to receive notifications and perform appropriate further actions.
3928 Since systems and what you expect them to do differ a lot, you can configure
3929 B<thresholds> for your values freely. This gives you a lot of flexibility but
3930 also a lot of responsibility.
3932 Every time a value is out of range a notification is dispatched. This means
3933 that the idle percentage of your CPU needs to be less then the configured
3934 threshold only once for a notification to be generated. There's no such thing
3935 as a moving average or similar - at least not now.
3937 Also, all values that match a threshold are considered to be relevant or
3938 "interesting". As a consequence collectd will issue a notification if they are
3939 not received for twice the last timeout of the values. If, for example, some
3940 hosts sends it's CPU statistics to the server every 60 seconds, a notification
3941 will be dispatched after about 120 seconds. It may take a little longer because
3942 the timeout is checked only once each B<Interval> on the server.
3944 When a value comes within range again or is received after it was missing, an
3945 "OKAY-notification" is dispatched.
3947 Here is a configuration example to get you started. Read below for more
3960 <Plugin "interface">
3977 WarningMin 100000000
3983 There are basically two types of configuration statements: The C<Host>,
3984 C<Plugin>, and C<Type> blocks select the value for which a threshold should be
3985 configured. The C<Plugin> and C<Type> blocks may be specified further using the
3986 C<Instance> option. You can combine the block by nesting the blocks, though
3987 they must be nested in the above order, i.E<nbsp>e. C<Host> may contain either
3988 C<Plugin> and C<Type> blocks, C<Plugin> may only contain C<Type> blocks and
3989 C<Type> may not contain other blocks. If multiple blocks apply to the same
3990 value the most specific block is used.
3992 The other statements specify the threshold to configure. They B<must> be
3993 included in a C<Type> block. Currently the following statements are recognized:
3997 =item B<FailureMax> I<Value>
3999 =item B<WarningMax> I<Value>
4001 Sets the upper bound of acceptable values. If unset defaults to positive
4002 infinity. If a value is greater than B<FailureMax> a B<FAILURE> notification
4003 will be created. If the value is greater than B<WarningMax> but less than (or
4004 equal to) B<FailureMax> a B<WARNING> notification will be created.
4006 =item B<FailureMin> I<Value>
4008 =item B<WarningMin> I<Value>
4010 Sets the lower bound of acceptable values. If unset defaults to negative
4011 infinity. If a value is less than B<FailureMin> a B<FAILURE> notification will
4012 be created. If the value is less than B<WarningMin> but greater than (or equal
4013 to) B<FailureMin> a B<WARNING> notification will be created.
4015 =item B<DataSource> I<DSName>
4017 Some data sets have more than one "data source". Interesting examples are the
4018 C<if_octets> data set, which has received (C<rx>) and sent (C<tx>) bytes and
4019 the C<disk_ops> data set, which holds C<read> and C<write> operations. The
4020 system load data set, C<load>, even has three data sources: C<shortterm>,
4021 C<midterm>, and C<longterm>.
4023 Normally, all data sources are checked against a configured threshold. If this
4024 is undesirable, or if you want to specify different limits for each data
4025 source, you can use the B<DataSource> option to have a threshold apply only to
4028 =item B<Invert> B<true>|B<false>
4030 If set to B<true> the range of acceptable values is inverted, i.E<nbsp>e.
4031 values between B<FailureMin> and B<FailureMax> (B<WarningMin> and
4032 B<WarningMax>) are not okay. Defaults to B<false>.
4034 =item B<Persist> B<true>|B<false>
4036 Sets how often notifications are generated. If set to B<true> one notification
4037 will be generated for each value that is out of the acceptable range. If set to
4038 B<false> (the default) then a notification is only generated if a value is out
4039 of range but the previous value was okay.
4041 This applies to missing values, too: If set to B<true> a notification about a
4042 missing value is generated once every B<Interval> seconds. If set to B<false>
4043 only one such notification is generated until the value appears again.
4045 =item B<Percentage> B<true>|B<false>
4047 If set to B<true>, the minimum and maximum values given are interpreted as
4048 percentage value, relative to the other data sources. This is helpful for
4049 example for the "df" type, where you may want to issue a warning when less than
4050 5E<nbsp>% of the total space is available. Defaults to B<false>.
4054 =head1 FILTER CONFIGURATION
4056 Starting with collectd 4.6 there is a powerful filtering infrastructure
4057 implemented in the daemon. The concept has mostly been copied from
4058 I<ip_tables>, the packet filter infrastructure for Linux. We'll use a similar
4059 terminology, so that users that are familiar with iptables feel right at home.
4063 The following are the terms used in the remainder of the filter configuration
4064 documentation. For an ASCII-art schema of the mechanism, see
4065 L<"General structure"> below.
4071 A I<match> is a criteria to select specific values. Examples are, of course, the
4072 name of the value or it's current value.
4074 Matches are implemented in plugins which you have to load prior to using the
4075 match. The name of such plugins starts with the "match_" prefix.
4079 A I<target> is some action that is to be performed with data. Such actions
4080 could, for example, be to change part of the value's identifier or to ignore
4081 the value completely.
4083 Some of these targets are built into the daemon, see L<"Built-in targets">
4084 below. Other targets are implemented in plugins which you have to load prior to
4085 using the target. The name of such plugins starts with the "target_" prefix.
4089 The combination of any number of matches and at least one target is called a
4090 I<rule>. The target actions will be performed for all values for which B<all>
4091 matches apply. If the rule does not have any matches associated with it, the
4092 target action will be performed for all values.
4096 A I<chain> is a list of rules and possibly default targets. The rules are tried
4097 in order and if one matches, the associated target will be called. If a value
4098 is handled by a rule, it depends on the target whether or not any subsequent
4099 rules are considered or if traversal of the chain is aborted, see
4100 L<"Flow control"> below. After all rules have been checked, the default targets
4105 =head2 General structure
4107 The following shows the resulting structure:
4114 +---------+ +---------+ +---------+ +---------+
4115 ! Rule !->! Match !->! Match !->! Target !
4116 +---------+ +---------+ +---------+ +---------+
4119 +---------+ +---------+ +---------+
4120 ! Rule !->! Target !->! Target !
4121 +---------+ +---------+ +---------+
4128 +---------+ +---------+ +---------+
4129 ! Rule !->! Match !->! Target !
4130 +---------+ +---------+ +---------+
4140 There are four ways to control which way a value takes through the filter
4147 The built-in B<jump> target can be used to "call" another chain, i.E<nbsp>e.
4148 process the value with another chain. When the called chain finishes, usually
4149 the next target or rule after the jump is executed.
4153 The stop condition, signaled for example by the built-in target B<stop>, causes
4154 all processing of the value to be stopped immediately.
4158 Causes processing in the current chain to be aborted, but processing of the
4159 value generally will continue. This means that if the chain was called via
4160 B<Jump>, the next target or rule after the jump will be executed. If the chain
4161 was not called by another chain, control will be returned to the daemon and it
4162 may pass the value to another chain.
4166 Most targets will signal the B<continue> condition, meaning that processing
4167 should continue normally. There is no special built-in target for this
4174 The configuration reflects this structure directly:
4176 PostCacheChain "PostCache"
4178 <Rule "ignore_mysql_show">
4181 Type "^mysql_command$"
4182 TypeInstance "^show_"
4192 The above configuration example will ignore all values where the plugin field
4193 is "mysql", the type is "mysql_command" and the type instance begins with
4194 "show_". All other values will be sent to the C<rrdtool> write plugin via the
4195 default target of the chain. Since this chain is run after the value has been
4196 added to the cache, the MySQL C<show_*> command statistics will be available
4197 via the C<unixsock> plugin.
4199 =head2 List of configuration options
4203 =item B<PreCacheChain> I<ChainName>
4205 =item B<PostCacheChain> I<ChainName>
4207 Configure the name of the "pre-cache chain" and the "post-cache chain". The
4208 argument is the name of a I<chain> that should be executed before and/or after
4209 the values have been added to the cache.
4211 To understand the implications, it's important you know what is going on inside
4212 I<collectd>. The following diagram shows how values are passed from the
4213 read-plugins to the write-plugins:
4219 + - - - - V - - - - +
4220 : +---------------+ :
4223 : +-------+-------+ :
4226 : +-------+-------+ : +---------------+
4227 : ! Cache !--->! Value Cache !
4228 : ! insert ! : +---+---+-------+
4229 : +-------+-------+ : ! !
4230 : ! ,------------' !
4232 : +-------+---+---+ : +-------+-------+
4233 : ! Post-Cache +--->! Write-Plugins !
4234 : ! Chain ! : +---------------+
4235 : +---------------+ :
4238 + - - - - - - - - - +
4240 After the values are passed from the "read" plugins to the dispatch functions,
4241 the pre-cache chain is run first. The values are added to the internal cache
4242 afterwards. The post-cache chain is run after the values have been added to the
4243 cache. So why is it such a huge deal if chains are run before or after the
4244 values have been added to this cache?
4246 Targets that change the identifier of a value list should be executed before
4247 the values are added to the cache, so that the name in the cache matches the
4248 name that is used in the "write" plugins. The C<unixsock> plugin, too, uses
4249 this cache to receive a list of all available values. If you change the
4250 identifier after the value list has been added to the cache, this may easily
4251 lead to confusion, but it's not forbidden of course.
4253 The cache is also used to convert counter values to rates. These rates are, for
4254 example, used by the C<value> match (see below). If you use the rate stored in
4255 the cache B<before> the new value is added, you will use the old, B<previous>
4256 rate. Write plugins may use this rate, too, see the C<csv> plugin, for example.
4257 The C<unixsock> plugin uses these rates too, to implement the C<GETVAL>
4260 Last but not last, the B<stop> target makes a difference: If the pre-cache
4261 chain returns the stop condition, the value will not be added to the cache and
4262 the post-cache chain will not be run.
4264 =item B<Chain> I<Name>
4266 Adds a new chain with a certain name. This name can be used to refer to a
4267 specific chain, for example to jump to it.
4269 Within the B<Chain> block, there can be B<Rule> blocks and B<Target> blocks.
4271 =item B<Rule> [I<Name>]
4273 Adds a new rule to the current chain. The name of the rule is optional and
4274 currently has no meaning for the daemon.
4276 Within the B<Rule> block, there may be any number of B<Match> blocks and there
4277 must be at least one B<Target> block.
4279 =item B<Match> I<Name>
4281 Adds a match to a B<Rule> block. The name specifies what kind of match should
4282 be performed. Available matches depend on the plugins that have been loaded.
4284 The arguments inside the B<Match> block are passed to the plugin implementing
4285 the match, so which arguments are valid here depends on the plugin being used.
4286 If you do not need any to pass any arguments to a match, you can use the
4291 Which is equivalent to:
4296 =item B<Target> I<Name>
4298 Add a target to a rule or a default target to a chain. The name specifies what
4299 kind of target is to be added. Which targets are available depends on the
4300 plugins being loaded.
4302 The arguments inside the B<Target> block are passed to the plugin implementing
4303 the target, so which arguments are valid here depends on the plugin being used.
4304 If you do not need any to pass any arguments to a target, you can use the
4309 This is the same as writing:
4316 =head2 Built-in targets
4318 The following targets are built into the core daemon and therefore need no
4319 plugins to be loaded:
4325 Signals the "return" condition, see the L<"Flow control"> section above. This
4326 causes the current chain to stop processing the value and returns control to
4327 the calling chain. The calling chain will continue processing targets and rules
4328 just after the B<jump> target (see below). This is very similar to the
4329 B<RETURN> target of iptables, see L<iptables(8)>.
4331 This target does not have any options.
4339 Signals the "stop" condition, see the L<"Flow control"> section above. This
4340 causes processing of the value to be aborted immediately. This is similar to
4341 the B<DROP> target of iptables, see L<iptables(8)>.
4343 This target does not have any options.
4351 Sends the value to "write" plugins.
4357 =item B<Plugin> I<Name>
4359 Name of the write plugin to which the data should be sent. This option may be
4360 given multiple times to send the data to more than one write plugin.
4364 If no plugin is explicitly specified, the values will be sent to all available
4375 Starts processing the rules of another chain, see L<"Flow control"> above. If
4376 the end of that chain is reached, or a stop condition is encountered,
4377 processing will continue right after the B<jump> target, i.E<nbsp>e. with the
4378 next target or the next rule. This is similar to the B<-j> command line option
4379 of iptables, see L<iptables(8)>.
4385 =item B<Chain> I<Name>
4387 Jumps to the chain I<Name>. This argument is required and may appear only once.
4399 =head2 Available matches
4405 Matches a value using regular expressions.
4411 =item B<Host> I<Regex>
4413 =item B<Plugin> I<Regex>
4415 =item B<PluginInstance> I<Regex>
4417 =item B<Type> I<Regex>
4419 =item B<TypeInstance> I<Regex>
4421 Match values where the given regular expressions match the various fields of
4422 the identifier of a value. If multiple regular expressions are given, B<all>
4423 regexen must match for a value to match.
4430 Host "customer[0-9]+"
4436 Matches values that have a time which differs from the time on the server.
4438 This match is mainly intended for servers that receive values over the
4439 C<network> plugin and write them to disk using the C<rrdtool> plugin. RRDtool
4440 is very sensitive to the timestamp used when updating the RRD files. In
4441 particular, the time must be ever increasing. If a misbehaving client sends one
4442 packet with a timestamp far in the future, all further packets with a correct
4443 time will be ignored because of that one packet. What's worse, such corrupted
4444 RRD files are hard to fix.
4446 This match lets one match all values B<outside> a specified time range
4447 (relative to the server's time), so you can use the B<stop> target (see below)
4448 to ignore the value, for example.
4454 =item B<Future> I<Seconds>
4456 Matches all values that are I<ahead> of the server's time by I<Seconds> or more
4457 seconds. Set to zero for no limit. Either B<Future> or B<Past> must be
4460 =item B<Past> I<Seconds>
4462 Matches all values that are I<behind> of the server's time by I<Seconds> or
4463 more seconds. Set to zero for no limit. Either B<Future> or B<Past> must be
4475 This example matches all values that are five minutes or more ahead of the
4476 server or one hour (or more) lagging behind.
4480 Matches the actual value of data sources against given minimumE<nbsp>/ maximum
4481 values. If a data-set consists of more than one data-source, all data-sources
4482 must match the specified ranges for a positive match.
4488 =item B<Min> I<Value>
4490 Sets the smallest value which still results in a match. If unset, behaves like
4493 =item B<Max> I<Value>
4495 Sets the largest value which still results in a match. If unset, behaves like
4498 =item B<Invert> B<true>|B<false>
4500 Inverts the selection. If the B<Min> and B<Max> settings result in a match,
4501 no-match is returned and vice versa. Please note that the B<Invert> setting
4502 only effects how B<Min> and B<Max> are applied to a specific value. Especially
4503 the B<DataSource> and B<Satisfy> settings (see below) are not inverted.
4505 =item B<DataSource> I<DSName> [I<DSName> ...]
4507 Select one or more of the data sources. If no data source is configured, all
4508 data sources will be checked. If the type handled by the match does not have a
4509 data source of the specified name(s), this will always result in no match
4510 (independent of the B<Invert> setting).
4512 =item B<Satisfy> B<Any>|B<All>
4514 Specifies how checking with several data sources is performed. If set to
4515 B<Any>, the match succeeds if one of the data sources is in the configured
4516 range. If set to B<All> the match only succeeds if all data sources are within
4517 the configured range. Default is B<All>.
4519 Usually B<All> is used for positive matches, B<Any> is used for negative
4520 matches. This means that with B<All> you usually check that all values are in a
4521 "good" range, while with B<Any> you check if any value is within a "bad" range
4522 (or outside the "good" range).
4526 Either B<Min> or B<Max>, but not both, may be unset.
4530 # Match all values smaller than or equal to 100. Matches only if all data
4531 # sources are below 100.
4537 # Match if the value of any data source is outside the range of 0 - 100.
4545 =item B<empty_counter>
4547 Matches all values with one or more data sources of type B<COUNTER> and where
4548 all counter values are zero. These counters usually I<never> increased since
4549 they started existing (and are therefore uninteresting), or got reset recently
4550 or overflowed and you had really, I<really> bad luck.
4552 Please keep in mind that ignoring such counters can result in confusing
4553 behavior: Counters which hardly ever increase will be zero for long periods of
4554 time. If the counter is reset for some reason (machine or service restarted,
4555 usually), the graph will be empty (NAN) for a long time. People may not
4560 =head2 Available targets
4564 =item B<notification>
4566 Creates and dispatches a notification.
4572 =item B<Message> I<String>
4574 This required option sets the message of the notification. The following
4575 placeholders will be replaced by an appropriate value:
4583 =item B<%{plugin_instance}>
4587 =item B<%{type_instance}>
4589 These placeholders are replaced by the identifier field of the same name.
4591 =item B<%{ds:>I<name>B<}>
4593 These placeholders are replaced by a (hopefully) human readable representation
4594 of the current rate of this data source. If you changed the instance name
4595 (using the B<set> or B<replace> targets, see below), it may not be possible to
4596 convert counter values to rates.
4600 Please note that these placeholders are B<case sensitive>!
4602 =item B<Severity> B<"FATAL">|B<"WARNING">|B<"OKAY">
4604 Sets the severity of the message. If omitted, the severity B<"WARNING"> is
4611 <Target "notification">
4612 Message "Oops, the %{type_instance} temperature is currently %{ds:value}!"
4618 Replaces parts of the identifier using regular expressions.
4624 =item B<Host> I<Regex> I<Replacement>
4626 =item B<Plugin> I<Regex> I<Replacement>
4628 =item B<PluginInstance> I<Regex> I<Replacement>
4630 =item B<TypeInstance> I<Regex> I<Replacement>
4632 Match the appropriate field with the given regular expression I<Regex>. If the
4633 regular expression matches, that part that matches is replaced with
4634 I<Replacement>. If multiple places of the input buffer match a given regular
4635 expression, only the first occurrence will be replaced.
4637 You can specify each option multiple times to use multiple regular expressions
4645 # Replace "example.net" with "example.com"
4646 Host "\\<example.net\\>" "example.com"
4648 # Strip "www." from hostnames
4654 Sets part of the identifier of a value to a given string.
4660 =item B<Host> I<String>
4662 =item B<Plugin> I<String>
4664 =item B<PluginInstance> I<String>
4666 =item B<TypeInstance> I<String>
4668 Set the appropriate field to the given string. The strings for plugin instance
4669 and type instance may be empty, the strings for host and plugin may not be
4670 empty. It's currently not possible to set the type of a value this way.
4677 PluginInstance "coretemp"
4678 TypeInstance "core3"
4683 =head2 Backwards compatibility
4685 If you use collectd with an old configuration, i.E<nbsp>e. one without a
4686 B<Chain> block, it will behave as it used to. This is equivalent to the
4687 following configuration:
4693 If you specify a B<PostCacheChain>, the B<write> target will not be added
4694 anywhere and you will have to make sure that it is called where appropriate. We
4695 suggest to add the above snippet as default target to your "PostCache" chain.
4699 Ignore all values, where the hostname does not contain a dot, i.E<nbsp>e. can't
4715 L<collectd-exec(5)>,
4716 L<collectd-perl(5)>,
4717 L<collectd-unixsock(5)>,
4730 Florian Forster E<lt>octo@verplant.orgE<gt>