1 collectd - System information collection daemon
2 =================================================
8 collectd is a small daemon which collects system information periodically
9 and provides mechanisms to store and monitor the values in a variety of
16 * collectd is able to collect the following data:
19 Apache server utilization: Number of bytes transfered, number of
20 requests handled and detailed scoreboard statistics
23 APC UPS Daemon: UPS charge, load, input/output/battery voltage, etc.
26 Sensors in Macs running Mac OS X / Darwin: Temperature, fanspeed and
30 Statistics about Ascent, a free server for the game `World of Warcraft'.
33 Batterycharge, -current and voltage of ACPI and PMU based laptop
37 Parse statistics from websites using regular expressions.
40 Name server and resolver statistics from the `statistics-channel'
41 interface of BIND 9.5, 9,6 and later.
44 CPU utilization: Time spent in the system, user, nice, idle, and related
48 CPU frequency (For laptops with speed step or a similar technology)
51 Executes SQL statements on various databases and interprets the returned
55 Mountpoint usage (Basically the values `df(1)' delivers)
58 Disk utilization: Sectors read/written, number of read/write actions,
59 average time an IO-operation took to complete.
62 DNS traffic: Query types, response codes, opcodes and traffic/octets
66 Email statistics: Count, traffic, spam scores and checks.
67 See collectd-email(5).
70 Amount of entropy available to the system.
73 Values gathered by a custom program or script.
77 Count the number of files in directories.
80 Harddisk temperatures using hddtempd.
83 Interface traffic: Number of octets, packets and errors for each
87 Iptables' counters: Number of bytes that were matched by a certain
91 IPMI (Intelligent Platform Management Interface) sensors information.
94 IPVS connection statistics (number of connections, octets and packets
95 for each service and destination).
96 See http://www.linuxvirtualserver.org/software/index.html.
99 IRQ counters: Frequency in which certain interrupts occur.
102 System load average over the last 1, 5 and 15 minutes.
105 CPU, disk and network I/O statistics from virtual machines.
108 Motherboard sensors: temperature, fanspeed and voltage information,
112 Statistics of the memcached distributed caching system.
113 <http://www.danga.com/memcached/>
116 Memory utilization: Memory occupied by running processes, page cache,
117 buffer cache and free.
120 Information provided by serial multimeters, such as the `Metex
124 MySQL server statistics: Commands issued, handlers triggered, thread
125 usage, query cache utilization and traffic/octets sent and received.
128 Very detailed Linux network interface and routing statistics. You can get
129 (detailed) information on interfaces, qdiscs, classes, and, if you can
130 make use of it, filters.
133 Receive values that were collected by other hosts. Large setups will
134 want to collect the data on one dedicated machine, and this is the
135 plugin of choice for that.
138 NFS Procedures: Which NFS command were called how often. Only NFSv2 and
142 Collects statistics from `nginx' (speak: engine X), a HTTP and mail
146 NTP daemon statistics: Local clock drift, offset to peers, etc.
149 Network UPS tools: UPS current, voltage, power, charge, utilisation,
150 temperature, etc. See upsd(8).
152 - onewire (EXPERIMENTAL!)
153 Read onewire sensors using the owcapu library of the owfs project.
154 Please read in collectd.conf(5) why this plugin is experimental.
157 RX and TX of each client in openvpn-status.log (status-version 2).
158 <http://openvpn.net/index.php/documentation/howto.html>
161 Query data from an Oracle database.
164 The perl plugin implements a Perl-interpreter into collectd. You can
165 write your own plugins in Perl and return arbitrary values using this
166 API. See collectd-perl(5).
169 Network latency: Time to reach the default gateway or another given
173 PostgreSQL database statistics: active server connections, transaction
174 numbers, block IO, table row manipulations.
177 PowerDNS name server statistics.
180 Process counts: Number of running, sleeping, zombie, ... processes.
183 RRDtool caching daemon (RRDcacheD) statistics.
186 System sensors, accessed using lm_sensors: Voltages, temperatures and
190 RX and TX of serial interfaces. Linux only; needs root privileges.
193 Read values from SNMP (Simple Network Management Protocol) enabled
194 network devices such as switches, routers, thermometers, rack monitoring
195 servers, etc. See collectd-snmp(5).
198 Pages swapped out onto harddisk or whatever is called `swap' by the OS..
201 Follows (tails) logfiles, parses them by lines and submits matched
205 Bytes and operations read and written on tape devices. Solaris only.
208 Number of TCP connections to specific local and remote ports.
211 TeamSpeak2 server statistics.
214 Linux ACPI thermal zone information.
217 Users currently logged in.
220 Virtual memory statistics, e. g. the number of page-ins/-outs or the
221 number of pagefaults.
224 System resources used by Linux VServers.
225 See <http://linux-vserver.org/>.
228 Link quality of wireless cards. Linux only.
231 Bitrate and frequency of music played with XMMS.
233 * Output can be written or send to various destinations by the following
237 Write to comma separated values (CSV) files. This needs lots of
238 diskspace but is extremely portable and can be analysed with almost
239 every program that can analyse anything. Even Microsoft's Excel..
242 Send the data to a remote host to save the data somehow. This is useful
243 for large setups where the data should be saved by a dedicated machine.
246 Of course the values are propagated to plugins written in Perl, too, so
247 you can easily do weird stuff with the plugins we didn't dare think of
248 ;) See collectd-perl(5).
251 Output to round-robin-database (RRD) files using the RRDtool caching
252 daemon (RRDcacheD) - see rrdcached(1). That daemon provides a general
253 implementation of the caching done by the `rrdtool' plugin.
256 Output to round-robin-database (RRD) files using librrd. See rrdtool(1).
257 This is likely the most popular destination for such values. Since
258 updates to RRD-files are somewhat expensive this plugin can cache
259 updates to the files and write a bunch of updates at once, which lessens
263 One can query the values from the unixsock plugin whenever they're
264 needed. Please read collectd-unixsock(5) for a description on how that's
267 * Logging is, as everything in collectd, provided by plugins. The following
268 plugins keep up informed about what's going on:
271 Writes logmessages to a file or STDOUT/STDERR.
274 Log messages are propagated to plugins written in Perl as well.
275 See collectd-perl(5).
278 Logs to the standard UNIX logging mechanism, syslog.
280 * Notifications can be handled by the following plugins:
283 Send a desktop notification to a notification daemon, as defined in
284 the Desktop Notification Specification. To actually display the
285 notifications, notification-daemon is required.
286 See http://www.galago-project.org/specs/notification/.
289 Send an E-mail with the notification message to the configured
293 Execute a program or script to handle the notification.
294 See collectd-exec(5).
297 Writes the notification message to a file or STDOUT/STDERR.
300 Send the notification to a remote host to handle it somehow.
303 Notifications are propagated to plugins written in Perl as well.
304 See collectd-perl(5).
306 * Value processing can be controlled using the "filter chain" infrastructure
307 and "matches" and "targets". The following plugins are available:
310 Match values by their identifier based on regular expressions.
313 Match values with an invalid timestamp.
316 Select values by their data sources' values.
318 - target_notification
319 Create and dispatch a notification.
322 Replace parts of an identifier using regular expressions.
325 Set (overwrite) entire parts of an identifier.
327 * Miscellaneous plugins:
330 Sets the hostname to an unique identifier. This is meant for setups
331 where each client may migrate to another physical host, possibly going
332 through one or more name changes in the process.
334 * Performance: Since collectd is running as a daemon it doesn't spend much
335 time starting up again and again. With the exception of the exec plugin no
336 processes are forked. Caching in output plugins, such as the rrdtool and
337 network plugins, makes sure your resources are used efficiently. Also,
338 since collectd is programmed multithreaded it benefits from hyperthreading
339 and multicore processors and makes sure that the daemon isn't idle if only
340 one plugins waits for an IO-operation to complete.
342 * Once set up, hardly any maintenance is necessary. Setup is kept as easy
343 as possible and the default values should be okay for most users.
349 * collectd's configuration file can be found at `sysconfdir'/collectd.conf.
350 Run `collectd -h' for a list of builtin defaults. See `collectd.conf(5)'
351 for a list of options and a syntax description.
353 * When the `csv' or `rrdtool' plugins are loaded they'll write the values to
354 files. The usual place for these files is beneath `/var/lib/collectd'.
356 * When using some of the plugins, collectd needs to run as user root, since
357 only root can do certain things, such as craft ICMP packages needed to ping
358 other hosts. collectd should NOT be installed setuid root since it can be
359 used to overwrite valuable files!
361 * Sample scripts to generate graphs reside in `contrib/' in the source
362 package or somewhere near `/usr/share/doc/collectd' in most distributions.
363 Please be aware that those script are meant as a starting point for your
364 own experiments.. Some of them require the `RRDs' Perl module.
365 (`librrds-perl' on Debian) If you have written a more sophisticated
366 solution please share it with us.
368 * The RRAs of the automatically created RRD files depend on the `step'
369 and `heartbeat' settings given. If change these settings you may need to
370 re-create the files, losing all data. Please be aware of that when changing
371 the values and read the rrdtool(1) manpage thoroughly.
374 collectd and chkrootkit
375 -----------------------
377 If you are using the `dns' plugin chkrootkit(1) will report collectd as a
378 packet sniffer ("<iface>: PACKET SNIFFER(/usr/sbin/collectd[<pid>])"). The
379 plugin captures all UDP packets on port 53 to analyze the DNS traffic. In
380 this case, collectd is a legitimate sniffer and the report should be
381 considered to be a false positive. However, you might want to check that
382 this really is collectd and not some other, illegitimate sniffer.
388 To compile collectd from source you will need:
390 * Usual suspects: C compiler, linker, preprocessor, make, ...
392 * A POSIX-threads (pthread) implementation.
393 Since gathering some statistics is slow (network connections, slow devices,
394 etc) the collectd is parallelized. The POSIX threads interface is being
395 used and should be found in various implementations for hopefully all
398 * CoreFoundation.framework and IOKit.framework (optional)
399 For compiling on Darwin in general and the `apple_sensors' plugin in
401 <http://developer.apple.com/corefoundation/>
403 * libclntsh (optional)
404 Used by the `oracle' plugin.
407 If you want to use the `apache', `ascent', `curl' or `nginx' plugin.
408 <http://curl.haxx.se/>
411 Used by the `dbi' plugin to connect to various databases.
412 <http://libdbi.sourceforge.net/>
414 * libesmtp (optional)
415 For the `notify_email' plugin.
416 <http://www.stafford.uklinux.net/libesmtp/>
419 If present, the uuid plugin will check for UUID from HAL.
420 <http://hal.freedesktop.org/>
422 * libiptc (optional, if not found a version shipped with this distribution
423 can be used if the Linux kernel headers are available)
424 For querying iptables counters.
425 <http://netfilter.org/>
427 * libmysqlclient (optional)
428 Unsurprisingly used by the `mysql' plugin.
429 <http://dev.mysql.com/>
431 * libnetlink (optional)
432 Used, obviously, for the `netlink' plugin.
433 <http://www.linuxfoundation.org/en/Net:Iproute2>
435 * libnetsnmp (optional)
436 For the `snmp' plugin.
437 <http://www.net-snmp.org/>
439 * libnotify (optional)
440 For the `notify_desktop' plugin.
441 <http://www.galago-project.org/>
443 * liboping (optional, if not found a version shipped with this distribution
445 Used by the `ping' plugin to send and receive ICMP packets.
446 <http://verplant.org/liboping/>
448 * libowcapi (optional)
449 Used by the `onewire' plugin to read values from onewire sensors (or the
451 <http://www.owfs.org/>
454 Used to capture packets by the `dns' plugin.
455 <http://www.tcpdump.org/>
458 Used by the `filter_pcre' plugin.
459 <http://www.pcre.org/>
462 Obviously used by the `perl' plugin. The library has to be compiled with
463 ithread support (introduced in Perl 5.6.0).
464 <http://www.perl.org/>
467 The PostgreSQL C client library used by the `postgresql' plugin.
468 <http://www.postgresql.org/>
471 Used by the `rrdtool' and `rrdcached' plugins. The latter requires RRDtool
472 client support which was added after version 1.3 of RRDtool. Versions 1.0,
473 1.2 and 1.3 are known to work with the `rrdtool' plugin.
474 <http://oss.oetiker.ch/rrdtool/>
476 * librt, libsocket, libkstat, libdevinfo (optional)
477 Various standard Solaris libraries which provide system functions.
478 <http://developers.sun.com/solaris/>
480 * libsensors (optional)
481 To read from `lm_sensors', see the `sensors' plugin.
482 <http://www.lm-sensors.org/>
484 * libstatgrab (optional)
485 Used by various plugins to collect statistics on systems other than Linux
487 <http://www.i-scream.org/libstatgrab/>
489 * libupsclient/nut (optional)
490 For the `nut' plugin which queries nut's `upsd'.
491 <http://networkupstools.org/>
494 Collect statistics from virtual machines.
495 <http://libvirt.org/>
498 Parse XML data. This is needed for the `ascent' and `libvirt' plugins.
499 <http://xmlsoft.org/>
502 <http://www.xmms.org/>
505 Configuring / Compiling / Installing
506 ------------------------------------
508 To configure, build and install collectd with the default settings, run
509 `./configure && make && make install'. For detailed, generic instructions
510 see INSTALL. For a complete list of configure options and their description,
511 run `./configure --help'.
513 By default, the configure script will check for all build dependencies and
514 disable all plugins whose requirements cannot be fulfilled (any other plugin
515 will be enabled). To enable a plugin, install missing dependencies (see
516 section `Prerequisites' above) and rerun `configure'. If you specify the
517 `--enable-<plugin>' configure option, the script will fail if the depen-
518 dencies for the specified plugin are not met. If you specify the
519 `--disable-<plugin>' configure option, the plugin will not be built. Both
520 options are meant for package maintainers and should not be used in everyday
523 By default, collectd will be installed into `/opt/collectd'. You can adjust
524 this setting by specifying the `--prefix' configure option - see INSTALL for
525 details. If you pass DESTDIR=<path> to `make install', <path> will be
526 prefixed to all installation directories. This might be useful when creating
527 packages for collectd.
533 To compile correctly collectd needs to be able to initialize static
534 variables to NAN (Not A Number). Some C libraries, especially the GNU
535 libc, have a problem with that.
537 Luckily, with GCC it's possible to work around that problem: One can define
538 NAN as being (0.0 / 0.0) and `isnan' as `f != f'. However, to test this
539 ``implementation'' the configure script needs to compile and run a short
540 test program. Obviously running a test program when doing a cross-
541 compilation is, well, challenging.
543 If you run into this problem, you can use the `--with-nan-emulation'
544 configure option to force the use of this implementation. We can't promise
545 that the compiled binary actually behaves as it should, but since NANs
546 are likely never passed to the libm you have a good chance to be lucky.
552 For questions, bugreports, development information and basically all other
553 concerns please send an email to collectd's mailinglist at
554 <collectd at verplant.org>.
556 For live discussion and more personal contact visit us in IRC, we're in
557 channel #collectd on freenode.
563 Florian octo Forster <octo at verplant.org>,
564 Sebastian tokkee Harl <sh at tokkee.org>,
565 and many contributors (see `AUTHORS').
567 Please send bugreports and patches to the mailinglist, see `Contact' above.