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 transferred, 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, fan speed and
30 Various sensors in the Aquaero 5 water cooling board made by Aquacomputer.
33 Statistics about Ascent, a free server for the game `World of Warcraft'.
36 Using digital barometer sensor MPL115A2 or MPL3115 from Freescale
37 provides absolute barometric pressure, air pressure reduced to sea level
41 Batterycharge, -current and voltage of ACPI and PMU based laptop
45 Name server and resolver statistics from the `statistics-channel'
46 interface of BIND 9.5, 9,6 and later.
49 CPU accounting information for process groups under Linux.
52 Number of nf_conntrack entries.
55 Number of context switches done by the operating system.
58 CPU utilization: Time spent in the system, user, nice, idle, and related
62 CPU frequency (For laptops with speed step or a similar technology)
65 Parse statistics from websites using regular expressions.
68 Retrieves JSON data via cURL and parses it according to user
72 Retrieves XML data via cURL and parses it according to user
76 Executes SQL statements on various databases and interprets the returned
80 Mountpoint usage (Basically the values `df(1)' delivers)
83 Disk utilization: Sectors read/written, number of read/write actions,
84 average time an IO-operation took to complete.
87 DNS traffic: Query types, response codes, opcodes and traffic/octets
91 Collect individual drbd resource statistics.
94 Email statistics: Count, traffic, spam scores and checks.
95 See collectd-email(5).
98 Amount of entropy available to the system.
101 Network interface card statistics.
104 Values gathered by a custom program or script.
105 See collectd-exec(5).
108 Count the number of files in directories.
111 Linux file-system based caching framework statistics.
114 Receive multicast traffic from Ganglia instances.
117 Hard disk temperatures using hddtempd.
120 Interface traffic: Number of octets, packets and errors for each
124 Iptables' counters: Number of bytes that were matched by a certain
128 IPMI (Intelligent Platform Management Interface) sensors information.
131 IPVS connection statistics (number of connections, octets and packets
132 for each service and destination).
133 See http://www.linuxvirtualserver.org/software/index.html.
136 IRQ counters: Frequency in which certain interrupts occur.
139 Integrates a `Java Virtual Machine' (JVM) to execute plugins in Java
140 bytecode. See “Configuring with libjvm” below.
143 System load average over the last 1, 5 and 15 minutes.
146 Detailed CPU statistics of the “Logical Partitions” virtualization
147 technique built into IBM's POWER processors.
150 Size of “Logical Volumes” (LV) and “Volume Groups” (VG) of Linux'
151 “Logical Volume Manager” (LVM).
154 Queries very detailed usage statistics from wireless LAN adapters and
155 interfaces that use the Atheros chipset and the MadWifi driver.
158 Motherboard sensors: temperature, fan speed and voltage information,
162 Linux software-RAID device information (number of active, failed, spare
166 Query and parse data from a memcache daemon (memcached).
169 Statistics of the memcached distributed caching system.
170 <http://www.danga.com/memcached/>
173 Memory utilization: Memory occupied by running processes, page cache,
174 buffer cache and free.
177 Collects CPU usage, memory usage, temperatures and power consumption from
178 Intel Many Integrated Core (MIC) CPUs.
181 Reads values from Modbus/TCP enabled devices. Supports reading values
182 from multiple "slaves" so gateway devices can be used.
185 Information provided by serial multimeters, such as the `Metex
189 MySQL server statistics: Commands issued, handlers triggered, thread
190 usage, query cache utilization and traffic/octets sent and received.
193 Plugin to query performance values from a NetApp storage system using the
194 “Manage ONTAP” SDK provided by NetApp.
197 Very detailed Linux network interface and routing statistics. You can get
198 (detailed) information on interfaces, qdiscs, classes, and, if you can
199 make use of it, filters.
202 Receive values that were collected by other hosts. Large setups will
203 want to collect the data on one dedicated machine, and this is the
204 plugin of choice for that.
207 NFS Procedures: Which NFS command were called how often. Only NFSv2 and
211 Collects statistics from `nginx' (speak: engine X), a HTTP and mail
215 NTP daemon statistics: Local clock drift, offset to peers, etc.
218 Network UPS tools: UPS current, voltage, power, charge, utilisation,
219 temperature, etc. See upsd(8).
222 Information about Non-Uniform Memory Access (NUMA).
225 Queries routing information from the “Optimized Link State Routing”
228 - onewire (EXPERIMENTAL!)
229 Read onewire sensors using the owcapu library of the owfs project.
230 Please read in collectd.conf(5) why this plugin is experimental.
233 Read monitoring information from OpenLDAP's cn=Monitor subtree.
236 RX and TX of each client in openvpn-status.log (status-version 2).
237 <http://openvpn.net/index.php/documentation/howto.html>
240 Query data from an Oracle database.
243 The perl plugin implements a Perl-interpreter into collectd. You can
244 write your own plugins in Perl and return arbitrary values using this
245 API. See collectd-perl(5).
248 Query statistics from BSD's packet filter "pf".
251 Receive and dispatch timing values from Pinba, a profiling extension for
255 Network latency: Time to reach the default gateway or another given
259 PostgreSQL database statistics: active server connections, transaction
260 numbers, block IO, table row manipulations.
263 PowerDNS name server statistics.
266 Process counts: Number of running, sleeping, zombie, ... processes.
269 Counts various aspects of network protocols such as IP, TCP, UDP, etc.
272 The python plugin implements a Python interpreter into collectd. This
273 makes it possible to write plugins in Python which are executed by
274 collectd without the need to start a heavy interpreter every interval.
275 See collectd-python(5) for details.
278 The redis plugin gathers information from a Redis server, including:
279 uptime, used memory, total connections etc.
282 Query interface and wireless registration statistics from RouterOS.
285 RRDtool caching daemon (RRDcacheD) statistics.
288 System sensors, accessed using lm_sensors: Voltages, temperatures and
292 RX and TX of serial interfaces. Linux only; needs root privileges.
295 Uses libsigrok as a backend, allowing any sigrok-supported device
296 to have its measurements fed to collectd. This includes multimeters,
297 sound level meters, thermometers, and much more.
300 Collect SMART statistics, notably load cycle count, temperature
304 Read values from SNMP (Simple Network Management Protocol) enabled
305 network devices such as switches, routers, thermometers, rack monitoring
306 servers, etc. See collectd-snmp(5).
309 Acts as a StatsD server, reading values sent over the network from StatsD
310 clients and calculating rates and other aggregates out of these values.
313 Pages swapped out onto hard disk or whatever is called `swap' by the OS..
316 Parse table-like structured files.
319 Follows (tails) log files, parses them by lines and submits matched
323 Follows (tails) files in CSV format, parses each line and submits
327 Bytes and operations read and written on tape devices. Solaris only.
330 Number of TCP connections to specific local and remote ports.
333 TeamSpeak2 server statistics.
336 Plugin to read values from `The Energy Detective' (TED).
339 Linux ACPI thermal zone information.
342 Reads the number of records and file size from a running Tokyo Tyrant
346 System uptime statistics.
349 Users currently logged in.
352 Various statistics from Varnish, an HTTP accelerator.
355 CPU, memory, disk and network I/O statistics from virtual machines.
358 Virtual memory statistics, e. g. the number of page-ins/-outs or the
359 number of pagefaults.
362 System resources used by Linux VServers.
363 See <http://linux-vserver.org/>.
366 Link quality of wireless cards. Linux only.
369 Bitrate and frequency of music played with XMMS.
372 Statistics for ZFS' “Adaptive Replacement Cache” (ARC).
374 * Output can be written or sent to various destinations by the following
378 Sends JSON-encoded data to an Advanced Message Queuing Protocol (AMQP)
379 server, such as RabbitMQ.
382 Write to comma separated values (CSV) files. This needs lots of
383 diskspace but is extremely portable and can be analysed with almost
384 every program that can analyse anything. Even Microsoft's Excel..
387 Send the data to a remote host to save the data somehow. This is useful
388 for large setups where the data should be saved by a dedicated machine.
391 Of course the values are propagated to plugins written in Perl, too, so
392 you can easily do weird stuff with the plugins we didn't dare think of
393 ;) See collectd-perl(5).
396 It's possible to implement write plugins in Python using the python
397 plugin. See collectd-python(5) for details.
400 Output to round-robin-database (RRD) files using the RRDtool caching
401 daemon (RRDcacheD) - see rrdcached(1). That daemon provides a general
402 implementation of the caching done by the `rrdtool' plugin.
405 Output to round-robin-database (RRD) files using librrd. See rrdtool(1).
406 This is likely the most popular destination for such values. Since
407 updates to RRD-files are somewhat expensive this plugin can cache
408 updates to the files and write a bunch of updates at once, which lessens
412 One can query the values from the unixsock plugin whenever they're
413 needed. Please read collectd-unixsock(5) for a description on how that's
417 Sends data to Carbon, the storage layer of Graphite using TCP or UDP. It
418 can be configured to avoid logging send errors (especially useful when
422 Sends data OpenTSDB, a scalable no master, no shared state time series
426 Sends the values collected by collectd to a web-server using HTTP POST
427 requests. The transmitted data is either in a form understood by the
428 Exec plugin or formatted in JSON.
431 Sends data to Apache Kafka, a distributed queue.
434 Sends data to MongoDB, a NoSQL database.
437 Sends the values to a Redis key-value database server.
440 Sends data to Riemann, a stream processing and monitoring system.
442 * Logging is, as everything in collectd, provided by plugins. The following
443 plugins keep up informed about what's going on:
446 Writes log messages to a file or STDOUT/STDERR.
449 Log messages are propagated to plugins written in Perl as well.
450 See collectd-perl(5).
453 It's possible to implement log plugins in Python using the python plugin.
454 See collectd-python(5) for details.
457 Logs to the standard UNIX logging mechanism, syslog.
460 Writes log messages formatted as logstash JSON events.
462 * Notifications can be handled by the following plugins:
465 Send a desktop notification to a notification daemon, as defined in
466 the Desktop Notification Specification. To actually display the
467 notifications, notification-daemon is required.
468 See http://www.galago-project.org/specs/notification/.
471 Send an E-mail with the notification message to the configured
475 Execute a program or script to handle the notification.
476 See collectd-exec(5).
479 Writes the notification message to a file or STDOUT/STDERR.
482 Send the notification to a remote host to handle it somehow.
485 Notifications are propagated to plugins written in Perl as well.
486 See collectd-perl(5).
489 It's possible to implement notification plugins in Python using the
490 python plugin. See collectd-python(5) for details.
492 * Value processing can be controlled using the "filter chain" infrastructure
493 and "matches" and "targets". The following plugins are available:
495 - match_empty_counter
496 Match counter values which are currently zero.
499 Match values using a hash function of the hostname.
502 Match values by their identifier based on regular expressions.
505 Match values with an invalid timestamp.
508 Select values by their data sources' values.
510 - target_notification
511 Create and dispatch a notification.
514 Replace parts of an identifier using regular expressions.
517 Scale (multiply) values by an arbitrary value.
520 Set (overwrite) entire parts of an identifier.
522 * Miscellaneous plugins:
525 Selects multiple value lists based on patterns or regular expressions
526 and creates new aggregated values lists from those.
529 Checks values against configured thresholds and creates notifications if
530 values are out of bounds. See collectd-threshold(5) for details.
533 Sets the hostname to a unique identifier. This is meant for setups
534 where each client may migrate to another physical host, possibly going
535 through one or more name changes in the process.
537 * Performance: Since collectd is running as a daemon it doesn't spend much
538 time starting up again and again. With the exception of the exec plugin no
539 processes are forked. Caching in output plugins, such as the rrdtool and
540 network plugins, makes sure your resources are used efficiently. Also,
541 since collectd is programmed multithreaded it benefits from hyper-threading
542 and multicore processors and makes sure that the daemon isn't idle if only
543 one plugin waits for an IO-operation to complete.
545 * Once set up, hardly any maintenance is necessary. Setup is kept as easy
546 as possible and the default values should be okay for most users.
552 * collectd's configuration file can be found at `sysconfdir'/collectd.conf.
553 Run `collectd -h' for a list of built-in defaults. See `collectd.conf(5)'
554 for a list of options and a syntax description.
556 * When the `csv' or `rrdtool' plugins are loaded they'll write the values to
557 files. The usual place for these files is beneath `/var/lib/collectd'.
559 * When using some of the plugins, collectd needs to run as user root, since
560 only root can do certain things, such as craft ICMP packages needed to ping
561 other hosts. collectd should NOT be installed setuid root since it can be
562 used to overwrite valuable files!
564 * Sample scripts to generate graphs reside in `contrib/' in the source
565 package or somewhere near `/usr/share/doc/collectd' in most distributions.
566 Please be aware that those script are meant as a starting point for your
567 own experiments.. Some of them require the `RRDs' Perl module.
568 (`librrds-perl' on Debian) If you have written a more sophisticated
569 solution please share it with us.
571 * The RRAs of the automatically created RRD files depend on the `step'
572 and `heartbeat' settings given. If change these settings you may need to
573 re-create the files, losing all data. Please be aware of that when changing
574 the values and read the rrdtool(1) manpage thoroughly.
577 collectd and chkrootkit
578 -----------------------
580 If you are using the `dns' plugin chkrootkit(1) will report collectd as a
581 packet sniffer ("<iface>: PACKET SNIFFER(/usr/sbin/collectd[<pid>])"). The
582 plugin captures all UDP packets on port 53 to analyze the DNS traffic. In
583 this case, collectd is a legitimate sniffer and the report should be
584 considered to be a false positive. However, you might want to check that
585 this really is collectd and not some other, illegitimate sniffer.
591 To compile collectd from source you will need:
593 * Usual suspects: C compiler, linker, preprocessor, make, ...
595 * A POSIX-threads (pthread) implementation.
596 Since gathering some statistics is slow (network connections, slow devices,
597 etc) collectd is parallelized. The POSIX threads interface is being
598 used and should be found in various implementations for hopefully all
601 * aerotools-ng (optional)
602 Used by the `aquaero' plugin. Currently, the `libaquaero5' library, which
603 is used by the `aerotools-ng' toolkit, is not compiled as a shared object
604 nor does it feature an installation routine. Therefore, you need to point
605 collectd's configure script at the source directory of the `aerotools-ng'
607 <https://github.com/lynix/aerotools-ng>
609 * CoreFoundation.framework and IOKit.framework (optional)
610 For compiling on Darwin in general and the `apple_sensors' plugin in
612 <http://developer.apple.com/corefoundation/>
614 * libclntsh (optional)
615 Used by the `oracle' plugin.
617 * libcredis (optional)
618 Used by the `redis' plugin. Please note that you require a 0.2.2 version
619 or higher. <http://code.google.com/p/credis/>
622 If you want to use the `apache', `ascent', `bind', `curl', `curl_json',
623 `curl_xml', `nginx', or `write_http' plugin.
624 <http://curl.haxx.se/>
627 Used by the `dbi' plugin to connect to various databases.
628 <http://libdbi.sourceforge.net/>
630 * libesmtp (optional)
631 For the `notify_email' plugin.
632 <http://www.stafford.uklinux.net/libesmtp/>
634 * libganglia (optional)
635 Used by the `gmond' plugin to process data received from Ganglia.
636 <http://ganglia.info/>
638 * libgcrypt (optional)
639 Used by the `network' plugin for encryption and authentication.
640 <http://www.gnupg.org/>
643 If present, the `uuid' plugin will check for UUID from HAL.
644 <http://hal.freedesktop.org/>
646 * libi2c-dev (optional)
647 Used for the plugin `barometer', provides just the i2c-dev.h header file
648 for user space i2c development.
651 For querying iptables counters.
652 <http://netfilter.org/>
655 Library that encapsulates the `Java Virtual Machine' (JVM). This library is
656 used by the `java' plugin to execute Java bytecode. See “Configuring with
658 <http://openjdk.java.net/> (and others)
661 Used by the `openldap' plugin.
662 <http://www.openldap.org/>
665 Used by the `lvm' plugin.
666 <ftp://sources.redhat.com/pub/lvm2/>
668 * libmemcached (optional)
669 Used by the `memcachec' plugin to connect to a memcache daemon.
670 <http://tangent.org/552/libmemcached.html>
673 Used by the `netlink' plugin.
674 <http://www.netfilter.org/projects/libmnl/>
676 * libmodbus (optional)
677 Used by the `modbus' plugin to communicate with Modbus/TCP devices. The
678 `modbus' plugin works with version 2.0.3 of the library – due to frequent
679 API changes other versions may or may not compile cleanly.
680 <http://www.libmodbus.org/>
682 * libmysqlclient (optional)
683 Unsurprisingly used by the `mysql' plugin.
684 <http://dev.mysql.com/>
686 * libnetapp (optional)
687 Required for the `netapp' plugin.
688 This library is part of the “Manage ONTAP SDK” published by NetApp.
690 * libnetsnmp (optional)
691 For the `snmp' plugin.
692 <http://www.net-snmp.org/>
694 * libnotify (optional)
695 For the `notify_desktop' plugin.
696 <http://www.galago-project.org/>
698 * libopenipmi (optional)
699 Used by the `ipmi' plugin to prove IPMI devices.
700 <http://openipmi.sourceforge.net/>
702 * liboping (optional)
703 Used by the `ping' plugin to send and receive ICMP packets.
704 <http://octo.it/liboping/>
706 * libowcapi (optional)
707 Used by the `onewire' plugin to read values from onewire sensors (or the
709 <http://www.owfs.org/>
712 Used to capture packets by the `dns' plugin.
713 <http://www.tcpdump.org/>
715 * libperfstat (optional)
716 Used by various plugins to gather statistics under AIX.
719 Obviously used by the `perl' plugin. The library has to be compiled with
720 ithread support (introduced in Perl 5.6.0).
721 <http://www.perl.org/>
724 The PostgreSQL C client library used by the `postgresql' plugin.
725 <http://www.postgresql.org/>
727 * libprotobuf-c, protoc-c (optional)
728 Used by the `pinba' plugin to generate a parser for the network packets
729 sent by the Pinba PHP extension, and by the `write_riemann' plugin to
730 generate events to be sent to a Riemann server.
731 <http://code.google.com/p/protobuf-c/>
733 * libpython (optional)
734 Used by the `python' plugin. Currently, Python 2.3 and later and Python 3
736 <http://www.python.org/>
738 * librabbitmq (optional; also called “rabbitmq-c”)
739 Used by the `amqp' plugin for AMQP connections, for example to RabbitMQ.
740 <http://hg.rabbitmq.com/rabbitmq-c/>
742 * librdkafka (optional; also called “rdkafka”)
743 Used by the `write_kafka' plugin for producing messages and sending them
745 <https://github.com/edenhill/librdkafka>
747 * librouteros (optional)
748 Used by the `routeros' plugin to connect to a device running `RouterOS'.
749 <http://octo.it/librouteros/>
752 Used by the `rrdtool' and `rrdcached' plugins. The latter requires RRDtool
753 client support which was added after version 1.3 of RRDtool. Versions 1.0,
754 1.2 and 1.3 are known to work with the `rrdtool' plugin.
755 <http://oss.oetiker.ch/rrdtool/>
757 * librt, libsocket, libkstat, libdevinfo (optional)
758 Various standard Solaris libraries which provide system functions.
759 <http://developers.sun.com/solaris/>
761 * libsensors (optional)
762 To read from `lm_sensors', see the `sensors' plugin.
763 <http://www.lm-sensors.org/>
765 * libsigrok (optional)
766 Used by the `sigrok' plugin. In addition, libsigrok depends on glib,
767 libzip, and optionally (depending on which drivers are enabled) on
768 libusb, libftdi and libudev.
770 * libstatgrab (optional)
771 Used by various plugins to collect statistics on systems other than Linux
773 <http://www.i-scream.org/libstatgrab/>
775 * libtokyotyrant (optional)
776 Used by the `tokyotyrant' plugin.
777 <http://1978th.net/tokyotyrant/>
779 * libupsclient/nut (optional)
780 For the `nut' plugin which queries nut's `upsd'.
781 <http://networkupstools.org/>
784 Collect statistics from virtual machines.
785 <http://libvirt.org/>
788 Parse XML data. This is needed for the `ascent', `bind', `curl_xml' and
790 <http://xmlsoft.org/>
793 <http://www.xmms.org/>
796 Parse JSON data. This is needed for the `curl_json' and `log_logstash'
798 <http://github.com/lloyd/yajl>
800 * libvarnish (optional)
801 Fetches statistics from a Varnish instance. This is needed for the
803 <http://varnish-cache.org>
805 Configuring / Compiling / Installing
806 ------------------------------------
808 To configure, build and install collectd with the default settings, run
809 `./configure && make && make install'. For detailed, generic instructions
810 see INSTALL. For a complete list of configure options and their description,
811 run `./configure --help'.
813 By default, the configure script will check for all build dependencies and
814 disable all plugins whose requirements cannot be fulfilled (any other plugin
815 will be enabled). To enable a plugin, install missing dependencies (see
816 section `Prerequisites' above) and rerun `configure'. If you specify the
817 `--enable-<plugin>' configure option, the script will fail if the depen-
818 dencies for the specified plugin are not met. In that case you can force the
819 plugin to be built using the `--enable-<plugin>=force' configure option.
820 This will most likely fail though unless you're working in a very unusual
821 setup and you really know what you're doing. If you specify the
822 `--disable-<plugin>' configure option, the plugin will not be built. If you
823 specify the `--enable-all-plugins' or `--disable-all-plugins' configure
824 options, all plugins will be enabled or disabled respectively by default.
825 Explicitly enabling or disabling a plugin overwrites the default for the
826 specified plugin. These options are meant for package maintainers and should
827 not be used in everyday situations.
829 By default, collectd will be installed into `/opt/collectd'. You can adjust
830 this setting by specifying the `--prefix' configure option - see INSTALL for
831 details. If you pass DESTDIR=<path> to `make install', <path> will be
832 prefixed to all installation directories. This might be useful when creating
833 packages for collectd.
835 Configuring with libjvm
836 -----------------------
838 To determine the location of the required files of a Java installation is not
839 an easy task, because the locations vary with your kernel (Linux, SunOS, …)
840 and with your architecture (x86, SPARC, …) and there is no ‘java-config’
841 script we could use. Configuration of the JVM library is therefore a bit
844 The easiest way to use the `--with-java=$JAVA_HOME' option, where
845 `$JAVA_HOME' is usually something like:
846 /usr/lib/jvm/java-1.5.0-sun-1.5.0.14
848 The configure script will then use find(1) to look for the following files:
854 If found, appropriate CPP-flags and LD-flags are set and the following
855 library checks succeed.
857 If this doesn't work for you, you have the possibility to specify CPP-flags,
858 C-flags and LD-flags for the ‘Java’ plugin by hand, using the following three
859 (environment) variables:
865 For example (shortened for demonstration purposes):
867 ./configure JAVA_CPPFLAGS="-I$JAVA_HOME/include -I$JAVA_HOME/include/linux"
869 Adding "-ljvm" to the JAVA_LDFLAGS is done automatically, you don't have to
875 To compile correctly collectd needs to be able to initialize static
876 variables to NAN (Not A Number). Some C libraries, especially the GNU
877 libc, have a problem with that.
879 Luckily, with GCC it's possible to work around that problem: One can define
880 NAN as being (0.0 / 0.0) and `isnan' as `f != f'. However, to test this
881 ``implementation'' the configure script needs to compile and run a short
882 test program. Obviously running a test program when doing a cross-
883 compilation is, well, challenging.
885 If you run into this problem, you can use the `--with-nan-emulation'
886 configure option to force the use of this implementation. We can't promise
887 that the compiled binary actually behaves as it should, but since NANs
888 are likely never passed to the libm you have a good chance to be lucky.
890 Likewise, collectd needs to know the layout of doubles in memory, in order
891 to craft uniform network packets over different architectures. For this, it
892 needs to know how to convert doubles into the memory layout used by x86. The
893 configure script tries to figure this out by compiling and running a few
894 small test programs. This is of course not possible when cross-compiling.
895 You can use the `--with-fp-layout' option to tell the configure script which
896 conversion method to assume. Valid arguments are:
898 * `nothing' (12345678 -> 12345678)
899 * `endianflip' (12345678 -> 87654321)
900 * `intswap' (12345678 -> 56781234)
906 For questions, bug reports, development information and basically all other
907 concerns please send an email to collectd's mailing list at
908 <list at collectd.org>.
910 For live discussion and more personal contact visit us in IRC, we're in
911 channel #collectd on freenode.
917 Florian octo Forster <octo at collectd.org>,
918 Sebastian tokkee Harl <sh at tokkee.org>,
919 and many contributors (see `AUTHORS').
921 Please send bug reports and patches to the mailing list, see `Contact'
projects / collectd.git / blob