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 Reads absolute barometric pressure, air pressure reduced to sea level and
37 temperature. Supported sensors are MPL115A2 and MPL3115 from Freescale
38 and BMP085 from Bosch.
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 Statistics from the Ceph distributed storage system.
52 CPU accounting information for process groups under Linux.
55 Chrony daemon statistics: Local clock drift, offset to peers, etc.
58 Event-based interface status.
61 Number of nf_conntrack entries.
64 Number of context switches done by the operating system.
67 CPU utilization: Time spent in the system, user, nice, idle, and related
71 CPU frequency (For laptops with speed step or a similar technology)
74 CPU sleep: Time spent in suspend (For mobile devices which enter suspend automatically)
77 Parse statistics from websites using regular expressions.
80 Retrieves JSON data via cURL and parses it according to user
84 Retrieves XML data via cURL and parses it according to user
88 Executes SQL statements on various databases and interprets the returned
92 Mountpoint usage (Basically the values `df(1)' delivers)
95 Disk utilization: Sectors read/written, number of read/write actions,
96 average time an IO-operation took to complete.
99 DNS traffic: Query types, response codes, opcodes and traffic/octets
103 Collect DPDK interface statistics.
104 See docs/BUILD.dpdkstat.md for detailed build instructions.
106 This plugin should be compiled with compiler defenses enabled, for
107 example -fstack-protector.
110 Collect individual drbd resource statistics.
113 Email statistics: Count, traffic, spam scores and checks.
114 See collectd-email(5).
117 Amount of entropy available to the system.
120 Network interface card statistics.
123 Values gathered by a custom program or script.
124 See collectd-exec(5).
127 File handles statistics.
130 Count the number of files in directories.
133 Linux file-system based caching framework statistics.
136 Receive multicast traffic from Ganglia instances.
139 Monitor gps related data through gpsd.
142 Monitor NVIDIA GPU statistics available through NVML.
145 Hard disk temperatures using hddtempd.
148 Report the number of used and free hugepages. More info on
149 hugepages can be found here:
150 https://www.kernel.org/doc/Documentation/vm/hugetlbpage.txt.
152 This plugin should be compiled with compiler defenses enabled, for
153 example -fstack-protector.
156 The intel_pmu plugin reads performance counters provided by the Linux
157 kernel perf interface. The plugin uses jevents library to resolve named
158 events to perf events and access perf interface.
161 The intel_rdt plugin collects information provided by monitoring features
162 of Intel Resource Director Technology (Intel(R) RDT) like Cache Monitoring
163 Technology (CMT), Memory Bandwidth Monitoring (MBM). These features
164 provide information about utilization of shared resources like last level
165 cache occupancy, local memory bandwidth usage, remote memory bandwidth
166 usage, instructions per clock.
167 <https://01.org/packet-processing/cache-monitoring-technology-memory-bandwidth-monitoring-cache-allocation-technology-code-and-data>
170 Interface traffic: Number of octets, packets and errors for each
174 IPC counters: semaphores used, number of allocated segments in shared
178 IPMI (Intelligent Platform Management Interface) sensors information.
181 Iptables' counters: Number of bytes that were matched by a certain
185 IPVS connection statistics (number of connections, octets and packets
186 for each service and destination).
187 See http://www.linuxvirtualserver.org/software/index.html.
190 IRQ counters: Frequency in which certain interrupts occur.
193 Integrates a `Java Virtual Machine' (JVM) to execute plugins in Java
195 See docs/BUILD.java.md for detailed build instructions.
198 System load average over the last 1, 5 and 15 minutes.
201 Detailed CPU statistics of the “Logical Partitions” virtualization
202 technique built into IBM's POWER processors.
205 The Lua plugin implements a Lua interpreter into collectd. This
206 makes it possible to write plugins in Lua which are executed by
207 collectd without the need to start a heavy interpreter every interval.
208 See collectd-lua(5) for details.
211 Size of “Logical Volumes” (LV) and “Volume Groups” (VG) of Linux'
212 “Logical Volume Manager” (LVM).
215 Queries very detailed usage statistics from wireless LAN adapters and
216 interfaces that use the Atheros chipset and the MadWifi driver.
219 Motherboard sensors: temperature, fan speed and voltage information,
223 Monitor machine check exceptions (hardware errors detected by hardware
224 and reported to software) reported by mcelog and generate appropriate
225 notifications when machine check exceptions are detected.
228 Linux software-RAID device information (number of active, failed, spare
232 Query and parse data from a memcache daemon (memcached).
235 Statistics of the memcached distributed caching system.
236 <http://www.danga.com/memcached/>
239 Memory utilization: Memory occupied by running processes, page cache,
240 buffer cache and free.
243 Collects CPU usage, memory usage, temperatures and power consumption from
244 Intel Many Integrated Core (MIC) CPUs.
247 Reads values from Modbus/TCP enabled devices. Supports reading values
248 from multiple "slaves" so gateway devices can be used.
251 Information provided by serial multimeters, such as the `Metex
255 MySQL server statistics: Commands issued, handlers triggered, thread
256 usage, query cache utilization and traffic/octets sent and received.
259 Plugin to query performance values from a NetApp storage system using the
260 “Manage ONTAP” SDK provided by NetApp.
263 Very detailed Linux network interface and routing statistics. You can get
264 (detailed) information on interfaces, qdiscs, classes, and, if you can
265 make use of it, filters.
268 Receive values that were collected by other hosts. Large setups will
269 want to collect the data on one dedicated machine, and this is the
270 plugin of choice for that.
273 NFS Procedures: Which NFS command were called how often.
276 Collects statistics from `nginx' (speak: engine X), a HTTP and mail
280 NTP daemon statistics: Local clock drift, offset to peers, etc.
283 Information about Non-Uniform Memory Access (NUMA).
286 Network UPS tools: UPS current, voltage, power, charge, utilisation,
287 temperature, etc. See upsd(8).
290 Queries routing information from the “Optimized Link State Routing”
293 - onewire (EXPERIMENTAL!)
294 Read onewire sensors using the owcapu library of the owfs project.
295 Please read in collectd.conf(5) why this plugin is experimental.
298 Read monitoring information from OpenLDAP's cn=Monitor subtree.
301 RX and TX of each client in openvpn-status.log (status-version 2).
302 <http://openvpn.net/index.php/documentation/howto.html>
305 Query data from an Oracle database.
308 The plugin monitors the link status of Open vSwitch (OVS) connected
309 interfaces, dispatches the values to collectd and sends the notification
310 whenever the link state change occurs in the OVS database. It requires
311 YAJL library to be installed.
312 Detailed instructions for installing and setting up Open vSwitch, see
314 <http://openvswitch.org/support/dist-docs/INSTALL.rst.html>
317 The plugin collects the statistics of OVS connected bridges and
318 interfaces. It requires YAJL library to be installed.
319 Detailed instructions for installing and setting up Open vSwitch, see
321 <http://openvswitch.org/support/dist-docs/INSTALL.rst.html>
324 Read errors from PCI Express Device Status and AER extended capabilities.
325 <https://www.design-reuse.com/articles/38374/pcie-error-logging-and-handling-on-a-typical-soc.html>
328 The perl plugin implements a Perl-interpreter into collectd. You can
329 write your own plugins in Perl and return arbitrary values using this
330 API. See collectd-perl(5).
333 Query statistics from BSD's packet filter "pf".
336 Receive and dispatch timing values from Pinba, a profiling extension for
340 Network latency: Time to reach the default gateway or another given
344 PostgreSQL database statistics: active server connections, transaction
345 numbers, block IO, table row manipulations.
348 PowerDNS name server statistics.
351 Process counts: Number of running, sleeping, zombie, ... processes.
354 Listens for process starts and exits via netlink.
357 Counts various aspects of network protocols such as IP, TCP, UDP, etc.
360 The python plugin implements a Python interpreter into collectd. This
361 makes it possible to write plugins in Python which are executed by
362 collectd without the need to start a heavy interpreter every interval.
363 See collectd-python(5) for details.
366 The redis plugin gathers information from a Redis server, including:
367 uptime, used memory, total connections etc.
370 Query interface and wireless registration statistics from RouterOS.
373 RRDtool caching daemon (RRDcacheD) statistics.
376 System sensors, accessed using lm_sensors: Voltages, temperatures and
380 RX and TX of serial interfaces. Linux only; needs root privileges.
383 Uses libsigrok as a backend, allowing any sigrok-supported device
384 to have its measurements fed to collectd. This includes multimeters,
385 sound level meters, thermometers, and much more.
388 Collect SMART statistics, notably load cycle count, temperature
392 Read values from SNMP (Simple Network Management Protocol) enabled
393 network devices such as switches, routers, thermometers, rack monitoring
394 servers, etc. See collectd-snmp(5).
397 Acts as a StatsD server, reading values sent over the network from StatsD
398 clients and calculating rates and other aggregates out of these values.
401 Listens to rsyslog events and submits matched values.
404 Pages swapped out onto hard disk or whatever is called `swap' by the OS..
407 Parse table-like structured files.
410 Follows (tails) log files, parses them by lines and submits matched
414 Follows (tails) files in CSV format, parses each line and submits
418 Bytes and operations read and written on tape devices. Solaris only.
421 Number of TCP connections to specific local and remote ports.
424 TeamSpeak2 server statistics.
427 Plugin to read values from `The Energy Detective' (TED).
430 Linux ACPI thermal zone information.
433 Reads the number of records and file size from a running Tokyo Tyrant
437 Reads CPU frequency and C-state residency on modern Intel
438 turbo-capable processors.
441 System uptime statistics.
444 Users currently logged in.
447 Various statistics from Varnish, an HTTP accelerator.
450 CPU, memory, disk and network I/O statistics from virtual machines.
453 Virtual memory statistics, e.g. the number of page-ins/-outs or the
454 number of pagefaults.
457 System resources used by Linux VServers.
458 See <http://linux-vserver.org/>.
461 Link quality of wireless cards. Linux only.
464 XEN Hypervisor CPU stats.
467 Bitrate and frequency of music played with XMMS.
470 Statistics for ZFS' “Adaptive Replacement Cache” (ARC).
473 Measures the percentage of cpu load per container (zone) under Solaris 10
477 Read data from Zookeeper's MNTR command.
479 * Output can be written or sent to various destinations by the following
483 Sends JSON-encoded data to an Advanced Message Queuing Protocol (AMQP)
484 0.9.1 server, such as RabbitMQ.
487 Sends JSON-encoded data to an Advanced Message Queuing Protocol (AMQP)
488 1.0 server, such as Qpid Dispatch Router or Apache Artemis Broker.
491 Write to comma separated values (CSV) files. This needs lots of
492 diskspace but is extremely portable and can be analysed with almost
493 every program that can analyse anything. Even Microsoft's Excel..
496 Send and receive values over the network using the gRPC framework.
499 It's possible to implement write plugins in Lua using the Lua
500 plugin. See collectd-lua(5) for details.
503 Publishes and subscribes to MQTT topics.
506 Send the data to a remote host to save the data somehow. This is useful
507 for large setups where the data should be saved by a dedicated machine.
510 Of course the values are propagated to plugins written in Perl, too, so
511 you can easily do weird stuff with the plugins we didn't dare think of
512 ;) See collectd-perl(5).
515 It's possible to implement write plugins in Python using the python
516 plugin. See collectd-python(5) for details.
519 Output to round-robin-database (RRD) files using the RRDtool caching
520 daemon (RRDcacheD) - see rrdcached(1). That daemon provides a general
521 implementation of the caching done by the `rrdtool' plugin.
524 Output to round-robin-database (RRD) files using librrd. See rrdtool(1).
525 This is likely the most popular destination for such values. Since
526 updates to RRD-files are somewhat expensive this plugin can cache
527 updates to the files and write a bunch of updates at once, which lessens
531 Receives and handles queries from SNMP master agent and returns the data
532 collected by read plugins. Handles requests only for OIDs specified in
533 configuration file. To handle SNMP queries the plugin gets data from
534 collectd and translates requested values from collectd's internal format
538 One can query the values from the unixsock plugin whenever they're
539 needed. Please read collectd-unixsock(5) for a description on how that's
543 Sends data to Carbon, the storage layer of Graphite using TCP or UDP. It
544 can be configured to avoid logging send errors (especially useful when
548 Sends the values collected by collectd to a web-server using HTTP POST
549 requests. The transmitted data is either in a form understood by the
550 Exec plugin or formatted in JSON.
553 Sends data to Apache Kafka, a distributed queue.
556 Writes data to the log
559 Sends data to MongoDB, a NoSQL database.
562 Publish values using an embedded HTTP server, in a format compatible
563 with Prometheus' collectd_exporter.
566 Sends the values to a Redis key-value database server.
569 Sends data to Riemann, a stream processing and monitoring system.
572 Sends data to Sensu, a stream processing and monitoring system, via the
573 Sensu client local TCP socket.
576 Sends data in syslog format, using TCP, where the message
577 contains the metric in human or JSON format.
580 Sends data OpenTSDB, a scalable no master, no shared state time series
583 * Logging is, as everything in collectd, provided by plugins. The following
584 plugins keep us informed about what's going on:
587 Writes log messages to a file or STDOUT/STDERR.
590 Log messages are propagated to plugins written in Perl as well.
591 See collectd-perl(5).
594 It's possible to implement log plugins in Python using the python plugin.
595 See collectd-python(5) for details.
598 Logs to the standard UNIX logging mechanism, syslog.
601 Writes log messages formatted as logstash JSON events.
603 * Notifications can be handled by the following plugins:
606 Send a desktop notification to a notification daemon, as defined in
607 the Desktop Notification Specification. To actually display the
608 notifications, notification-daemon is required.
609 See http://www.galago-project.org/specs/notification/.
612 Send an E-mail with the notification message to the configured
616 Submit notifications as passive check results to a local nagios instance.
619 Execute a program or script to handle the notification.
620 See collectd-exec(5).
623 Writes the notification message to a file or STDOUT/STDERR.
626 Send the notification to a remote host to handle it somehow.
629 Notifications are propagated to plugins written in Perl as well.
630 See collectd-perl(5).
633 It's possible to implement notification plugins in Python using the
634 python plugin. See collectd-python(5) for details.
636 * Value processing can be controlled using the "filter chain" infrastructure
637 and "matches" and "targets". The following plugins are available:
639 - match_empty_counter
640 Match counter values which are currently zero.
643 Match values using a hash function of the hostname.
646 Match values by their identifier based on regular expressions.
649 Match values with an invalid timestamp.
652 Select values by their data sources' values.
654 - target_notification
655 Create and dispatch a notification.
658 Replace parts of an identifier using regular expressions.
661 Scale (multiply) values by an arbitrary value.
664 Set (overwrite) entire parts of an identifier.
666 * Miscellaneous plugins:
669 Selects multiple value lists based on patterns or regular expressions
670 and creates new aggregated values lists from those.
673 Checks values against configured thresholds and creates notifications if
674 values are out of bounds. See collectd-threshold(5) for details.
677 Sets the hostname to a unique identifier. This is meant for setups
678 where each client may migrate to another physical host, possibly going
679 through one or more name changes in the process.
681 * Performance: Since collectd is running as a daemon it doesn't spend much
682 time starting up again and again. With the exception of the exec plugin no
683 processes are forked. Caching in output plugins, such as the rrdtool and
684 network plugins, makes sure your resources are used efficiently. Also,
685 since collectd is programmed multithreaded it benefits from hyper-threading
686 and multicore processors and makes sure that the daemon isn't idle if only
687 one plugin waits for an IO-operation to complete.
689 * Once set up, hardly any maintenance is necessary. Setup is kept as easy
690 as possible and the default values should be okay for most users.
696 * collectd's configuration file can be found at `sysconfdir'/collectd.conf.
697 Run `collectd -h' for a list of built-in defaults. See `collectd.conf(5)'
698 for a list of options and a syntax description.
700 * When the `csv' or `rrdtool' plugins are loaded they'll write the values to
701 files. The usual place for these files is beneath `/var/lib/collectd'.
703 * When using some of the plugins, collectd needs to run as user root, since
704 only root can do certain things, such as craft ICMP packages needed to ping
705 other hosts. collectd should NOT be installed setuid root since it can be
706 used to overwrite valuable files!
708 * Sample scripts to generate graphs reside in `contrib/' in the source
709 package or somewhere near `/usr/share/doc/collectd' in most distributions.
710 Please be aware that those script are meant as a starting point for your
711 own experiments.. Some of them require the `RRDs' Perl module.
712 (`librrds-perl' on Debian) If you have written a more sophisticated
713 solution please share it with us.
715 * The RRAs of the automatically created RRD files depend on the `step'
716 and `heartbeat' settings given. If change these settings you may need to
717 re-create the files, losing all data. Please be aware of that when changing
718 the values and read the rrdtool(1) manpage thoroughly.
721 collectd and chkrootkit
722 -----------------------
724 If you are using the `dns' plugin chkrootkit(1) will report collectd as a
725 packet sniffer ("<iface>: PACKET SNIFFER(/usr/sbin/collectd[<pid>])"). The
726 plugin captures all UDP packets on port 53 to analyze the DNS traffic. In
727 this case, collectd is a legitimate sniffer and the report should be
728 considered to be a false positive. However, you might want to check that
729 this really is collectd and not some other, illegitimate sniffer.
735 To compile collectd from source you will need:
737 * Usual suspects: C compiler, linker, preprocessor, make, ...
739 collectd makes use of some common C99 features, e.g. compound literals and
740 mixed declarations, and therefore requires a C99 compatible compiler.
742 On Debian and Ubuntu, the "build-essential" package should pull in
743 everything that's necessary.
745 * A POSIX-threads (pthread) implementation.
746 Since gathering some statistics is slow (network connections, slow devices,
747 etc) collectd is parallelized. The POSIX threads interface is being
748 used and should be found in various implementations for hopefully all
751 * When building from the Git repository, flex (tokenizer) and bison (parser
752 generator) are required. Release tarballs include the generated files – you
753 don't need these packages in that case.
755 * aerotools-ng (optional)
756 Used by the `aquaero' plugin. Currently, the `libaquaero5' library, which
757 is used by the `aerotools-ng' toolkit, is not compiled as a shared object
758 nor does it feature an installation routine. Therefore, you need to point
759 collectd's configure script at the source directory of the `aerotools-ng'
761 <https://github.com/lynix/aerotools-ng>
763 * CoreFoundation.framework and IOKit.framework (optional)
764 For compiling on Darwin in general and the `apple_sensors' plugin in
766 <http://developer.apple.com/corefoundation/>
769 Used by the `gpu_nvidia' plugin
770 <https://developer.nvidia.com/cuda-downloads>
772 * libatasmart (optional)
773 Used by the `smart' plugin.
774 <http://git.0pointer.de/?p=libatasmart.git>
777 The `turbostat' plugin can optionally build Linux Capabilities support,
778 which avoids full privileges requirement (aka. running as root) to read
780 <http://sites.google.com/site/fullycapable/>
782 * libclntsh (optional)
783 Used by the `oracle' plugin.
785 * libhiredis (optional)
786 Used by the redis plugin. Please note that you require a 0.10.0 version
787 or higher. <https://github.com/redis/hiredis>
790 If you want to use the `apache', `ascent', `bind', `curl', `curl_json',
791 `curl_xml', `nginx', or `write_http' plugin.
792 <http://curl.haxx.se/>
795 Used by the `dbi' plugin to connect to various databases.
796 <http://libdbi.sourceforge.net/>
798 * libesmtp (optional)
799 For the `notify_email' plugin.
800 <http://www.stafford.uklinux.net/libesmtp/>
802 * libganglia (optional)
803 Used by the `gmond' plugin to process data received from Ganglia.
804 <http://ganglia.info/>
807 Used by the `grpc' plugin. gRPC requires a C++ compiler supporting the
811 * libgcrypt (optional)
812 Used by the `network' plugin for encryption and authentication.
813 <http://www.gnupg.org/>
816 Used by the `gps' plugin.
817 <http://developer.berlios.de/projects/gpsd/>
819 * libi2c-dev (optional)
820 Used for the plugin `barometer', provides just the i2c-dev.h header file
821 for user space i2c development.
824 For querying iptables counters.
825 <http://netfilter.org/>
827 * libjevents (optional)
828 The jevents library is used by the `intel_pmu' plugin to access the Linux
829 kernel perf interface.
830 Note: the library should be build with -fPIC flag to be linked with
831 intel_pmu shared object correctly.
832 <https://github.com/andikleen/pmu-tools>
835 Library that encapsulates the `Java Virtual Machine' (JVM). This library is
836 used by the `java' plugin to execute Java bytecode.
837 See docs/BUILD.java.md for detailed build instructions.
838 <http://openjdk.java.net/> (and others)
841 Used by the `openldap' plugin.
842 <http://www.openldap.org/>
845 Used by the `lua' plugin. Currently, Lua 5.1 and later are supported.
846 <https://www.lua.org/>
849 Used by the `lvm' plugin.
850 <ftp://sources.redhat.com/pub/lvm2/>
852 * libmemcached (optional)
853 Used by the `memcachec' plugin to connect to a memcache daemon.
854 <http://tangent.org/552/libmemcached.html>
856 * libmicrohttpd (optional)
857 Used by the write_prometheus plugin to run an http daemon.
858 <http://www.gnu.org/software/libmicrohttpd/>
861 Used by the `netlink' plugin.
862 <http://www.netfilter.org/projects/libmnl/>
864 * libmodbus (optional)
865 Used by the `modbus' plugin to communicate with Modbus/TCP devices. The
866 `modbus' plugin works with version 2.0.3 of the library – due to frequent
867 API changes other versions may or may not compile cleanly.
868 <http://www.libmodbus.org/>
870 * libmysqlclient (optional)
871 Unsurprisingly used by the `mysql' plugin.
872 <http://dev.mysql.com/>
874 * libnetapp (optional)
875 Required for the `netapp' plugin.
876 This library is part of the “Manage ONTAP SDK” published by NetApp.
878 * libnetsnmp (optional)
879 For the `snmp' and 'snmp_agent' plugins.
880 <http://www.net-snmp.org/>
882 * libnetsnmpagent (optional)
883 Required for the 'snmp_agent' plugin.
884 <http://www.net-snmp.org/>
886 * libnotify (optional)
887 For the `notify_desktop' plugin.
888 <http://www.galago-project.org/>
890 * libopenipmi (optional)
891 Used by the `ipmi' plugin to prove IPMI devices.
892 <http://openipmi.sourceforge.net/>
894 * liboping (optional)
895 Used by the `ping' plugin to send and receive ICMP packets.
896 <http://octo.it/liboping/>
898 * libowcapi (optional)
899 Used by the `onewire' plugin to read values from onewire sensors (or the
901 <http://www.owfs.org/>
904 Used to capture packets by the `dns' plugin.
905 <http://www.tcpdump.org/>
907 * libperfstat (optional)
908 Used by various plugins to gather statistics under AIX.
911 Obviously used by the `perl' plugin. The library has to be compiled with
912 ithread support (introduced in Perl 5.6.0).
913 <http://www.perl.org/>
916 The PostgreSQL C client library used by the `postgresql' plugin.
917 <http://www.postgresql.org/>
920 The PQoS library for Intel(R) Resource Director Technology used by the
922 <https://github.com/01org/intel-cmt-cat>
924 * libprotobuf, protoc 3.0+ (optional)
925 Used by the `grpc' plugin to generate service stubs and code to handle
926 network packets of collectd's protobuf-based network protocol.
927 <https://developers.google.com/protocol-buffers/>
929 * libprotobuf-c, protoc-c (optional)
930 Used by the `pinba' plugin to generate a parser for the network packets
931 sent by the Pinba PHP extension.
932 <http://code.google.com/p/protobuf-c/>
934 * libpython (optional)
935 Used by the `python' plugin. Currently, Python 2.6 and later and Python 3
937 <http://www.python.org/>
939 * libqpid-proton (optional)
940 Used by the `amqp1' plugin for AMQP 1.0 connections, for example to
942 <http://qpid.apache.org/>
944 * librabbitmq (optional; also called “rabbitmq-c”)
945 Used by the `amqp' plugin for AMQP 0.9.1 connections, for example to
947 <http://hg.rabbitmq.com/rabbitmq-c/>
949 * librdkafka (optional; also called “rdkafka”)
950 Used by the `write_kafka' plugin for producing messages and sending them
952 <https://github.com/edenhill/librdkafka>
954 * librouteros (optional)
955 Used by the `routeros' plugin to connect to a device running `RouterOS'.
956 <http://octo.it/librouteros/>
959 Used by the `rrdtool' and `rrdcached' plugins. The latter requires RRDtool
960 client support which was added after version 1.3 of RRDtool. Versions 1.0,
961 1.2 and 1.3 are known to work with the `rrdtool' plugin.
962 <http://oss.oetiker.ch/rrdtool/>
964 * librt, libsocket, libkstat, libdevinfo (optional)
965 Various standard Solaris libraries which provide system functions.
966 <http://developers.sun.com/solaris/>
968 * libsensors (optional)
969 To read from `lm_sensors', see the `sensors' plugin.
970 <http://www.lm-sensors.org/>
972 * libsigrok (optional)
973 Used by the `sigrok' plugin. In addition, libsigrok depends on glib,
974 libzip, and optionally (depending on which drivers are enabled) on
975 libusb, libftdi and libudev.
977 * libstatgrab (optional)
978 Used by various plugins to collect statistics on systems other than Linux
980 <http://www.i-scream.org/libstatgrab/>
982 * libtokyotyrant (optional)
983 Used by the `tokyotyrant' plugin.
984 <http://1978th.net/tokyotyrant/>
986 * libupsclient/nut (optional)
987 For the `nut' plugin which queries nut's `upsd'.
988 <http://networkupstools.org/>
991 Collect statistics from virtual machines.
992 <http://libvirt.org/>
995 Parse XML data. This is needed for the `ascent', `bind', `curl_xml' and
997 <http://xmlsoft.org/>
1000 Used by the `xencpu' plugin.
1001 <http://xenbits.xensource.com/>
1003 * libxmms (optional)
1004 <http://www.xmms.org/>
1006 * libyajl (optional)
1007 Parse JSON data. This is needed for the `ceph', `curl_json', 'ovs_events',
1008 'ovs_stats' and `log_logstash' plugins.
1009 <http://github.com/lloyd/yajl>
1011 * libvarnish (optional)
1012 Fetches statistics from a Varnish instance. This is needed for the
1014 <http://varnish-cache.org>
1016 * riemann-c-client (optional)
1017 For the `write_riemann' plugin.
1018 <https://github.com/algernon/riemann-c-client>
1020 Configuring / Compiling / Installing
1021 ------------------------------------
1023 To configure, build and install collectd with the default settings, run
1024 `./configure && make && make install'. For a complete list of configure
1025 options and their description, run `./configure --help'.
1027 By default, the configure script will check for all build dependencies and
1028 disable all plugins whose requirements cannot be fulfilled (any other plugin
1029 will be enabled). To enable a plugin, install missing dependencies (see
1030 section `Prerequisites' above) and rerun `configure'. If you specify the
1031 `--enable-<plugin>' configure option, the script will fail if the depen-
1032 dencies for the specified plugin are not met. In that case you can force the
1033 plugin to be built using the `--enable-<plugin>=force' configure option.
1034 This will most likely fail though unless you're working in a very unusual
1035 setup and you really know what you're doing. If you specify the
1036 `--disable-<plugin>' configure option, the plugin will not be built. If you
1037 specify the `--enable-all-plugins' or `--disable-all-plugins' configure
1038 options, all plugins will be enabled or disabled respectively by default.
1039 Explicitly enabling or disabling a plugin overwrites the default for the
1040 specified plugin. These options are meant for package maintainers and should
1041 not be used in everyday situations.
1043 By default, collectd will be installed into `/opt/collectd'. You can adjust
1044 this setting by specifying the `--prefix' configure option - see INSTALL for
1045 details. If you pass DESTDIR=<path> to `make install', <path> will be
1046 prefixed to all installation directories. This might be useful when creating
1047 packages for collectd.
1049 Generating the configure script
1050 -------------------------------
1052 Collectd ships with a `build.sh' script to generate the `configure'
1053 script shipped with releases.
1055 To generate the `configure` script, you'll need the following dependencies:
1064 The `build.sh' script takes no arguments.
1068 -----------------------------------------------
1070 Collectd can be built on Windows using Cygwin, and the result is a binary that
1071 runs natively on Windows. That is, Cygwin is only needed for building, not running,
1074 You will need to install the following Cygwin packages:
1081 - mingw64-x86_64-dlfcn
1082 - mingw64-x86_64-gcc-core
1083 - mingw64-x86_64-zlib
1086 To build, just run the `build.sh' script in your Cygwin terminal. By default, it installs
1087 to "C:/Program Files/collectd". You can change the location by setting the INSTALL_DIR
1090 $ export INSTALL_DIR="C:/some/other/install/directory"
1095 $ INSTALL_DIR="C:/some/other/install/directory" ./build.sh
1101 To compile correctly collectd needs to be able to initialize static
1102 variables to NAN (Not A Number). Some C libraries, especially the GNU
1103 libc, have a problem with that.
1105 Luckily, with GCC it's possible to work around that problem: One can define
1106 NAN as being (0.0 / 0.0) and `isnan' as `f != f'. However, to test this
1107 ``implementation'' the configure script needs to compile and run a short
1108 test program. Obviously running a test program when doing a cross-
1109 compilation is, well, challenging.
1111 If you run into this problem, you can use the `--with-nan-emulation'
1112 configure option to force the use of this implementation. We can't promise
1113 that the compiled binary actually behaves as it should, but since NANs
1114 are likely never passed to the libm you have a good chance to be lucky.
1116 Likewise, collectd needs to know the layout of doubles in memory, in order
1117 to craft uniform network packets over different architectures. For this, it
1118 needs to know how to convert doubles into the memory layout used by x86. The
1119 configure script tries to figure this out by compiling and running a few
1120 small test programs. This is of course not possible when cross-compiling.
1121 You can use the `--with-fp-layout' option to tell the configure script which
1122 conversion method to assume. Valid arguments are:
1124 * `nothing' (12345678 -> 12345678)
1125 * `endianflip' (12345678 -> 87654321)
1126 * `intswap' (12345678 -> 56781234)
1132 Please use GitHub to report bugs and submit pull requests:
1133 <https://github.com/collectd/collectd/>.
1134 See CONTRIBUTING.md for details.
1136 For questions, development information and basically all other concerns please
1137 send an email to collectd's mailing list at
1138 <list at collectd.org>.
1140 For live discussion and more personal contact visit us in IRC, we're in
1141 channel #collectd on freenode.
1147 Florian octo Forster <octo at collectd.org>,
1148 Sebastian tokkee Harl <sh at tokkee.org>,
1149 and many contributors (see `AUTHORS').
projects / collectd.git / blob