1 collectd - System information collection daemon
2 =================================================
3 https://collectd.org/
5 About
6 -----
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
10 ways.
13 Features
14 --------
16 * collectd is able to collect the following data:
18 - apache
19 Apache server utilization: Number of bytes transferred, number of
20 requests handled and detailed scoreboard statistics
22 - apcups
23 APC UPS Daemon: UPS charge, load, input/output/battery voltage, etc.
25 - apple_sensors
26 Sensors in Macs running Mac OS X / Darwin: Temperature, fan speed and
27 voltage sensors.
29 - aquaero
30 Various sensors in the Aquaero 5 water cooling board made by Aquacomputer.
32 - ascent
33 Statistics about Ascent, a free server for the game `World of Warcraft'.
35 - barometer
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.
40 - battery
41 Batterycharge, -current and voltage of ACPI and PMU based laptop
42 batteries.
44 - bind
45 Name server and resolver statistics from the `statistics-channel'
46 interface of BIND 9.5, 9,6 and later.
48 - ceph
49 Statistics from the Ceph distributed storage system.
51 - cgroups
52 CPU accounting information for process groups under Linux.
54 - chrony
55 Chrony daemon statistics: Local clock drift, offset to peers, etc.
57 - conntrack
58 Number of nf_conntrack entries.
60 - contextswitch
61 Number of context switches done by the operating system.
63 - cpu
64 CPU utilization: Time spent in the system, user, nice, idle, and related
65 states.
67 - cpufreq
68 CPU frequency (For laptops with speed step or a similar technology)
70 - cpusleep
71 CPU sleep: Time spent in suspend (For mobile devices which enter suspend automatically)
73 - curl
74 Parse statistics from websites using regular expressions.
76 - curl_json
77 Retrieves JSON data via cURL and parses it according to user
78 configuration.
80 - curl_xml
81 Retrieves XML data via cURL and parses it according to user
82 configuration.
84 - dbi
85 Executes SQL statements on various databases and interprets the returned
86 data.
88 - df
89 Mountpoint usage (Basically the values `df(1)' delivers)
91 - disk
92 Disk utilization: Sectors read/written, number of read/write actions,
93 average time an IO-operation took to complete.
95 - dns
96 DNS traffic: Query types, response codes, opcodes and traffic/octets
97 transferred.
99 - drbd
100 Collect individual drbd resource statistics.
102 - email
103 Email statistics: Count, traffic, spam scores and checks.
104 See collectd-email(5).
106 - entropy
107 Amount of entropy available to the system.
109 - ethstat
110 Network interface card statistics.
112 - exec
113 Values gathered by a custom program or script.
114 See collectd-exec(5).
116 - fhcount
117 File handles statistics.
119 - filecount
120 Count the number of files in directories.
122 - fscache
123 Linux file-system based caching framework statistics.
125 - gmond
126 Receive multicast traffic from Ganglia instances.
128 - gps
129 Monitor gps related data through gpsd.
131 - grpc
132 Receive values over the network using the gRPC framework.
134 - hddtemp
135 Hard disk temperatures using hddtempd.
137 - interface
138 Interface traffic: Number of octets, packets and errors for each
139 interface.
141 - ipc
142 IPC counters: semaphores used, number of allocated segments in shared
143 memory and more.
145 - ipmi
146 IPMI (Intelligent Platform Management Interface) sensors information.
148 - iptables
149 Iptables' counters: Number of bytes that were matched by a certain
150 iptables rule.
152 - ipvs
153 IPVS connection statistics (number of connections, octets and packets
154 for each service and destination).
155 See http://www.linuxvirtualserver.org/software/index.html.
157 - irq
158 IRQ counters: Frequency in which certain interrupts occur.
160 - java
161 Integrates a `Java Virtual Machine' (JVM) to execute plugins in Java
162 bytecode. See “Configuring with libjvm” below.
164 - load
165 System load average over the last 1, 5 and 15 minutes.
167 - lpar
168 Detailed CPU statistics of the “Logical Partitions” virtualization
169 technique built into IBM's POWER processors.
171 - lvm
172 Size of “Logical Volumes” (LV) and “Volume Groups” (VG) of Linux'
173 “Logical Volume Manager” (LVM).
175 - madwifi
176 Queries very detailed usage statistics from wireless LAN adapters and
177 interfaces that use the Atheros chipset and the MadWifi driver.
179 - mbmon
180 Motherboard sensors: temperature, fan speed and voltage information,
181 using mbmon(1).
183 - md
184 Linux software-RAID device information (number of active, failed, spare
185 and missing disks).
187 - memcachec
188 Query and parse data from a memcache daemon (memcached).
190 - memcached
191 Statistics of the memcached distributed caching system.
192 <http://www.danga.com/memcached/>
194 - memory
195 Memory utilization: Memory occupied by running processes, page cache,
196 buffer cache and free.
198 - mic
199 Collects CPU usage, memory usage, temperatures and power consumption from
200 Intel Many Integrated Core (MIC) CPUs.
202 - modbus
203 Reads values from Modbus/TCP enabled devices. Supports reading values
204 from multiple "slaves" so gateway devices can be used.
206 - mqtt
207 Publishes and subscribes to MQTT topics.
209 - multimeter
210 Information provided by serial multimeters, such as the `Metex
211 M-4650CR'.
213 - mysql
214 MySQL server statistics: Commands issued, handlers triggered, thread
215 usage, query cache utilization and traffic/octets sent and received.
217 - netapp
218 Plugin to query performance values from a NetApp storage system using the
219 “Manage ONTAP” SDK provided by NetApp.
221 - netlink
222 Very detailed Linux network interface and routing statistics. You can get
223 (detailed) information on interfaces, qdiscs, classes, and, if you can
224 make use of it, filters.
226 - network
227 Receive values that were collected by other hosts. Large setups will
228 want to collect the data on one dedicated machine, and this is the
229 plugin of choice for that.
231 - nfs
232 NFS Procedures: Which NFS command were called how often. Only NFSv2 and
233 NFSv3 right now.
235 - nginx
236 Collects statistics from `nginx' (speak: engine X), a HTTP and mail
237 server/proxy.
239 - ntpd
240 NTP daemon statistics: Local clock drift, offset to peers, etc.
242 - numa
243 Information about Non-Uniform Memory Access (NUMA).
245 - nut
246 Network UPS tools: UPS current, voltage, power, charge, utilisation,
247 temperature, etc. See upsd(8).
249 - olsrd
250 Queries routing information from the “Optimized Link State Routing”
251 daemon.
253 - onewire (EXPERIMENTAL!)
254 Read onewire sensors using the owcapu library of the owfs project.
255 Please read in collectd.conf(5) why this plugin is experimental.
257 - openldap
258 Read monitoring information from OpenLDAP's cn=Monitor subtree.
260 - openvpn
261 RX and TX of each client in openvpn-status.log (status-version 2).
262 <http://openvpn.net/index.php/documentation/howto.html>
264 - oracle
265 Query data from an Oracle database.
267 - perl
268 The perl plugin implements a Perl-interpreter into collectd. You can
269 write your own plugins in Perl and return arbitrary values using this
270 API. See collectd-perl(5).
272 - pf
273 Query statistics from BSD's packet filter "pf".
275 - pinba
276 Receive and dispatch timing values from Pinba, a profiling extension for
277 PHP.
279 - ping
280 Network latency: Time to reach the default gateway or another given
281 host.
283 - postgresql
284 PostgreSQL database statistics: active server connections, transaction
285 numbers, block IO, table row manipulations.
287 - powerdns
288 PowerDNS name server statistics.
290 - processes
291 Process counts: Number of running, sleeping, zombie, ... processes.
293 - protocols
294 Counts various aspects of network protocols such as IP, TCP, UDP, etc.
296 - python
297 The python plugin implements a Python interpreter into collectd. This
298 makes it possible to write plugins in Python which are executed by
299 collectd without the need to start a heavy interpreter every interval.
300 See collectd-python(5) for details.
302 - redis
303 The redis plugin gathers information from a Redis server, including:
304 uptime, used memory, total connections etc.
306 - routeros
307 Query interface and wireless registration statistics from RouterOS.
309 - rrdcached
310 RRDtool caching daemon (RRDcacheD) statistics.
312 - sensors
313 System sensors, accessed using lm_sensors: Voltages, temperatures and
314 fan rotation speeds.
316 - serial
317 RX and TX of serial interfaces. Linux only; needs root privileges.
319 - sigrok
320 Uses libsigrok as a backend, allowing any sigrok-supported device
321 to have its measurements fed to collectd. This includes multimeters,
322 sound level meters, thermometers, and much more.
324 - smart
325 Collect SMART statistics, notably load cycle count, temperature
326 and bad sectors.
328 - snmp
329 Read values from SNMP (Simple Network Management Protocol) enabled
330 network devices such as switches, routers, thermometers, rack monitoring
331 servers, etc. See collectd-snmp(5).
333 - statsd
334 Acts as a StatsD server, reading values sent over the network from StatsD
335 clients and calculating rates and other aggregates out of these values.
337 - swap
338 Pages swapped out onto hard disk or whatever is called `swap' by the OS..
340 - table
341 Parse table-like structured files.
343 - tail
344 Follows (tails) log files, parses them by lines and submits matched
345 values.
347 - tail_csv
348 Follows (tails) files in CSV format, parses each line and submits
349 extracted values.
351 - tape
352 Bytes and operations read and written on tape devices. Solaris only.
354 - tcpconns
355 Number of TCP connections to specific local and remote ports.
357 - teamspeak2
358 TeamSpeak2 server statistics.
360 - ted
361 Plugin to read values from `The Energy Detective' (TED).
363 - thermal
364 Linux ACPI thermal zone information.
366 - tokyotyrant
367 Reads the number of records and file size from a running Tokyo Tyrant
368 server.
370 - turbostat
371 Reads CPU frequency and C-state residency on modern Intel
372 turbo-capable processors.
374 - uptime
375 System uptime statistics.
377 - users
378 Users currently logged in.
380 - varnish
381 Various statistics from Varnish, an HTTP accelerator.
383 - virt
384 CPU, memory, disk and network I/O statistics from virtual machines.
386 - vmem
387 Virtual memory statistics, e. g. the number of page-ins/-outs or the
388 number of pagefaults.
390 - vserver
391 System resources used by Linux VServers.
392 See <http://linux-vserver.org/>.
394 - wireless
395 Link quality of wireless cards. Linux only.
397 - xencpu
398 XEN Hypervisor CPU stats.
400 - xmms
401 Bitrate and frequency of music played with XMMS.
403 - zfs_arc
404 Statistics for ZFS' “Adaptive Replacement Cache” (ARC).
406 - zone
407 Measures the percentage of cpu load per container (zone) under Solaris 10
408 and higher
410 - zookeeper
411 Read data from Zookeeper's MNTR command.
413 * Output can be written or sent to various destinations by the following
414 plugins:
416 - amqp
417 Sends JSON-encoded data to an Advanced Message Queuing Protocol (AMQP)
418 server, such as RabbitMQ.
420 - csv
421 Write to comma separated values (CSV) files. This needs lots of
422 diskspace but is extremely portable and can be analysed with almost
423 every program that can analyse anything. Even Microsoft's Excel..
425 - network
426 Send the data to a remote host to save the data somehow. This is useful
427 for large setups where the data should be saved by a dedicated machine.
429 - perl
430 Of course the values are propagated to plugins written in Perl, too, so
431 you can easily do weird stuff with the plugins we didn't dare think of
432 ;) See collectd-perl(5).
434 - python
435 It's possible to implement write plugins in Python using the python
436 plugin. See collectd-python(5) for details.
438 - rrdcached
439 Output to round-robin-database (RRD) files using the RRDtool caching
440 daemon (RRDcacheD) - see rrdcached(1). That daemon provides a general
441 implementation of the caching done by the `rrdtool' plugin.
443 - rrdtool
444 Output to round-robin-database (RRD) files using librrd. See rrdtool(1).
445 This is likely the most popular destination for such values. Since
446 updates to RRD-files are somewhat expensive this plugin can cache
447 updates to the files and write a bunch of updates at once, which lessens
448 system load a lot.
450 - unixsock
451 One can query the values from the unixsock plugin whenever they're
452 needed. Please read collectd-unixsock(5) for a description on how that's
453 done.
455 - write_graphite
456 Sends data to Carbon, the storage layer of Graphite using TCP or UDP. It
457 can be configured to avoid logging send errors (especially useful when
458 using UDP).
460 - write_http
461 Sends the values collected by collectd to a web-server using HTTP POST
462 requests. The transmitted data is either in a form understood by the
463 Exec plugin or formatted in JSON.
465 - write_kafka
466 Sends data to Apache Kafka, a distributed queue.
468 - write_log
469 Writes data to the log
471 - write_mongodb
472 Sends data to MongoDB, a NoSQL database.
474 - write_redis
475 Sends the values to a Redis key-value database server.
477 - write_riemann
478 Sends data to Riemann, a stream processing and monitoring system.
480 - write_sensu
481 Sends data to Sensu, a stream processing and monitoring system, via the
482 Sensu client local TCP socket.
484 - write_tsdb
485 Sends data OpenTSDB, a scalable no master, no shared state time series
486 database.
488 * Logging is, as everything in collectd, provided by plugins. The following
489 plugins keep us informed about what's going on:
491 - logfile
492 Writes log messages to a file or STDOUT/STDERR.
494 - perl
495 Log messages are propagated to plugins written in Perl as well.
496 See collectd-perl(5).
498 - python
499 It's possible to implement log plugins in Python using the python plugin.
500 See collectd-python(5) for details.
502 - syslog
503 Logs to the standard UNIX logging mechanism, syslog.
505 - log_logstash
506 Writes log messages formatted as logstash JSON events.
508 * Notifications can be handled by the following plugins:
510 - notify_desktop
511 Send a desktop notification to a notification daemon, as defined in
512 the Desktop Notification Specification. To actually display the
513 notifications, notification-daemon is required.
514 See http://www.galago-project.org/specs/notification/.
516 - notify_email
517 Send an E-mail with the notification message to the configured
518 recipients.
520 - notify_nagios
521 Submit notifications as passive check results to a local nagios instance.
523 - exec
524 Execute a program or script to handle the notification.
525 See collectd-exec(5).
527 - logfile
528 Writes the notification message to a file or STDOUT/STDERR.
530 - network
531 Send the notification to a remote host to handle it somehow.
533 - perl
534 Notifications are propagated to plugins written in Perl as well.
535 See collectd-perl(5).
537 - python
538 It's possible to implement notification plugins in Python using the
539 python plugin. See collectd-python(5) for details.
541 * Value processing can be controlled using the "filter chain" infrastructure
542 and "matches" and "targets". The following plugins are available:
544 - match_empty_counter
545 Match counter values which are currently zero.
547 - match_hashed
548 Match values using a hash function of the hostname.
550 - match_regex
551 Match values by their identifier based on regular expressions.
553 - match_timediff
554 Match values with an invalid timestamp.
556 - match_value
557 Select values by their data sources' values.
559 - target_notification
560 Create and dispatch a notification.
562 - target_replace
563 Replace parts of an identifier using regular expressions.
565 - target_scale
566 Scale (multiply) values by an arbitrary value.
568 - target_set
569 Set (overwrite) entire parts of an identifier.
571 * Miscellaneous plugins:
573 - aggregation
574 Selects multiple value lists based on patterns or regular expressions
575 and creates new aggregated values lists from those.
577 - threshold
578 Checks values against configured thresholds and creates notifications if
579 values are out of bounds. See collectd-threshold(5) for details.
581 - uuid
582 Sets the hostname to a unique identifier. This is meant for setups
583 where each client may migrate to another physical host, possibly going
584 through one or more name changes in the process.
586 * Performance: Since collectd is running as a daemon it doesn't spend much
587 time starting up again and again. With the exception of the exec plugin no
588 processes are forked. Caching in output plugins, such as the rrdtool and
589 network plugins, makes sure your resources are used efficiently. Also,
590 since collectd is programmed multithreaded it benefits from hyper-threading
591 and multicore processors and makes sure that the daemon isn't idle if only
592 one plugin waits for an IO-operation to complete.
594 * Once set up, hardly any maintenance is necessary. Setup is kept as easy
595 as possible and the default values should be okay for most users.
598 Operation
599 ---------
601 * collectd's configuration file can be found at `sysconfdir'/collectd.conf.
602 Run `collectd -h' for a list of built-in defaults. See `collectd.conf(5)'
603 for a list of options and a syntax description.
605 * When the `csv' or `rrdtool' plugins are loaded they'll write the values to
606 files. The usual place for these files is beneath `/var/lib/collectd'.
608 * When using some of the plugins, collectd needs to run as user root, since
609 only root can do certain things, such as craft ICMP packages needed to ping
610 other hosts. collectd should NOT be installed setuid root since it can be
611 used to overwrite valuable files!
613 * Sample scripts to generate graphs reside in `contrib/' in the source
614 package or somewhere near `/usr/share/doc/collectd' in most distributions.
615 Please be aware that those script are meant as a starting point for your
616 own experiments.. Some of them require the `RRDs' Perl module.
617 (`librrds-perl' on Debian) If you have written a more sophisticated
618 solution please share it with us.
620 * The RRAs of the automatically created RRD files depend on the `step'
621 and `heartbeat' settings given. If change these settings you may need to
622 re-create the files, losing all data. Please be aware of that when changing
623 the values and read the rrdtool(1) manpage thoroughly.
626 collectd and chkrootkit
627 -----------------------
629 If you are using the `dns' plugin chkrootkit(1) will report collectd as a
630 packet sniffer ("<iface>: PACKET SNIFFER(/usr/sbin/collectd[<pid>])"). The
631 plugin captures all UDP packets on port 53 to analyze the DNS traffic. In
632 this case, collectd is a legitimate sniffer and the report should be
633 considered to be a false positive. However, you might want to check that
634 this really is collectd and not some other, illegitimate sniffer.
637 Prerequisites
638 -------------
640 To compile collectd from source you will need:
642 * Usual suspects: C compiler, linker, preprocessor, make, ...
644 * A POSIX-threads (pthread) implementation.
645 Since gathering some statistics is slow (network connections, slow devices,
646 etc) collectd is parallelized. The POSIX threads interface is being
647 used and should be found in various implementations for hopefully all
648 platforms.
650 * aerotools-ng (optional)
651 Used by the `aquaero' plugin. Currently, the `libaquaero5' library, which
652 is used by the `aerotools-ng' toolkit, is not compiled as a shared object
653 nor does it feature an installation routine. Therefore, you need to point
654 collectd's configure script at the source directory of the `aerotools-ng'
655 project.
656 <https://github.com/lynix/aerotools-ng>
658 * CoreFoundation.framework and IOKit.framework (optional)
659 For compiling on Darwin in general and the `apple_sensors' plugin in
660 particular.
661 <http://developer.apple.com/corefoundation/>
663 * libatasmart (optional)
664 Used by the `smart' plugin.
665 <http://git.0pointer.de/?p=libatasmart.git>
667 * libcap (optional)
668 The `turbostat' plugin can optionally build Linux Capabilities support,
669 which avoids full privileges requirement (aka. running as root) to read
670 values.
671 <http://sites.google.com/site/fullycapable/>
673 * libclntsh (optional)
674 Used by the `oracle' plugin.
676 * libhiredis (optional)
677 Used by the redis plugin. Please note that you require a 0.10.0 version
678 or higher. <https://github.com/redis/hiredis>
680 * libcurl (optional)
681 If you want to use the `apache', `ascent', `bind', `curl', `curl_json',
682 `curl_xml', `nginx', or `write_http' plugin.
683 <http://curl.haxx.se/>
685 * libdbi (optional)
686 Used by the `dbi' plugin to connect to various databases.
687 <http://libdbi.sourceforge.net/>
689 * libesmtp (optional)
690 For the `notify_email' plugin.
691 <http://www.stafford.uklinux.net/libesmtp/>
693 * libganglia (optional)
694 Used by the `gmond' plugin to process data received from Ganglia.
695 <http://ganglia.info/>
697 * libgrpc (optional)
698 Used by the `grpc' plugin. gRPC requires a C++ compiler supporting the
699 C++11 standard.
700 <https://grpc.io/>
702 * libgcrypt (optional)
703 Used by the `network' plugin for encryption and authentication.
704 <http://www.gnupg.org/>
706 * libgps (optional)
707 Used by the `gps' plugin.
708 <http://developer.berlios.de/projects/gpsd/>
710 * libhal (optional)
711 If present, the `uuid' plugin will check for UUID from HAL.
712 <http://hal.freedesktop.org/>
714 * libi2c-dev (optional)
715 Used for the plugin `barometer', provides just the i2c-dev.h header file
716 for user space i2c development.
718 * libiptc (optional)
719 For querying iptables counters.
720 <http://netfilter.org/>
722 * libjvm (optional)
723 Library that encapsulates the `Java Virtual Machine' (JVM). This library is
724 used by the `java' plugin to execute Java bytecode. See “Configuring with
725 libjvm” below.
726 <http://openjdk.java.net/> (and others)
728 * libldap (optional)
729 Used by the `openldap' plugin.
730 <http://www.openldap.org/>
732 * liblvm2 (optional)
733 Used by the `lvm' plugin.
734 <ftp://sources.redhat.com/pub/lvm2/>
736 * libmemcached (optional)
737 Used by the `memcachec' plugin to connect to a memcache daemon.
738 <http://tangent.org/552/libmemcached.html>
740 * libmnl (optional)
741 Used by the `netlink' plugin.
742 <http://www.netfilter.org/projects/libmnl/>
744 * libmodbus (optional)
745 Used by the `modbus' plugin to communicate with Modbus/TCP devices. The
746 `modbus' plugin works with version 2.0.3 of the library – due to frequent
747 API changes other versions may or may not compile cleanly.
748 <http://www.libmodbus.org/>
750 * libmysqlclient (optional)
751 Unsurprisingly used by the `mysql' plugin.
752 <http://dev.mysql.com/>
754 * libnetapp (optional)
755 Required for the `netapp' plugin.
756 This library is part of the “Manage ONTAP SDK” published by NetApp.
758 * libnetsnmp (optional)
759 For the `snmp' plugin.
760 <http://www.net-snmp.org/>
762 * libnotify (optional)
763 For the `notify_desktop' plugin.
764 <http://www.galago-project.org/>
766 * libopenipmi (optional)
767 Used by the `ipmi' plugin to prove IPMI devices.
768 <http://openipmi.sourceforge.net/>
770 * liboping (optional)
771 Used by the `ping' plugin to send and receive ICMP packets.
772 <http://octo.it/liboping/>
774 * libowcapi (optional)
775 Used by the `onewire' plugin to read values from onewire sensors (or the
776 owserver(1) daemon).
777 <http://www.owfs.org/>
779 * libpcap (optional)
780 Used to capture packets by the `dns' plugin.
781 <http://www.tcpdump.org/>
783 * libperfstat (optional)
784 Used by various plugins to gather statistics under AIX.
786 * libperl (optional)
787 Obviously used by the `perl' plugin. The library has to be compiled with
788 ithread support (introduced in Perl 5.6.0).
789 <http://www.perl.org/>
791 * libpq (optional)
792 The PostgreSQL C client library used by the `postgresql' plugin.
793 <http://www.postgresql.org/>
795 * libprotobuf, protoc 3.0+ (optional)
796 Used by the `grpc' plugin to generate service stubs and code to handle
797 network packets of collectd's protobuf-based network protocol.
798 <https://developers.google.com/protocol-buffers/>
800 * libprotobuf-c, protoc-c (optional)
801 Used by the `pinba' plugin to generate a parser for the network packets
802 sent by the Pinba PHP extension.
803 <http://code.google.com/p/protobuf-c/>
805 * libpython (optional)
806 Used by the `python' plugin. Currently, Python 2.3 and later and Python 3
807 are supported.
808 <http://www.python.org/>
810 * librabbitmq (optional; also called “rabbitmq-c”)
811 Used by the `amqp' plugin for AMQP connections, for example to RabbitMQ.
812 <http://hg.rabbitmq.com/rabbitmq-c/>
814 * librdkafka (optional; also called “rdkafka”)
815 Used by the `write_kafka' plugin for producing messages and sending them
816 to a Kafka broker.
817 <https://github.com/edenhill/librdkafka>
819 * librouteros (optional)
820 Used by the `routeros' plugin to connect to a device running `RouterOS'.
821 <http://octo.it/librouteros/>
823 * librrd (optional)
824 Used by the `rrdtool' and `rrdcached' plugins. The latter requires RRDtool
825 client support which was added after version 1.3 of RRDtool. Versions 1.0,
826 1.2 and 1.3 are known to work with the `rrdtool' plugin.
827 <http://oss.oetiker.ch/rrdtool/>
829 * librt, libsocket, libkstat, libdevinfo (optional)
830 Various standard Solaris libraries which provide system functions.
831 <http://developers.sun.com/solaris/>
833 * libsensors (optional)
834 To read from `lm_sensors', see the `sensors' plugin.
835 <http://www.lm-sensors.org/>
837 * libsigrok (optional)
838 Used by the `sigrok' plugin. In addition, libsigrok depends on glib,
839 libzip, and optionally (depending on which drivers are enabled) on
840 libusb, libftdi and libudev.
842 * libstatgrab (optional)
843 Used by various plugins to collect statistics on systems other than Linux
844 and/or Solaris.
845 <http://www.i-scream.org/libstatgrab/>
847 * libtokyotyrant (optional)
848 Used by the `tokyotyrant' plugin.
849 <http://1978th.net/tokyotyrant/>
851 * libupsclient/nut (optional)
852 For the `nut' plugin which queries nut's `upsd'.
853 <http://networkupstools.org/>
855 * libvirt (optional)
856 Collect statistics from virtual machines.
857 <http://libvirt.org/>
859 * libxml2 (optional)
860 Parse XML data. This is needed for the `ascent', `bind', `curl_xml' and
861 `virt' plugins.
862 <http://xmlsoft.org/>
864 * libxen (optional)
865 Used by the `xencpu' plugin.
866 <http://xenbits.xensource.com/>
868 * libxmms (optional)
869 <http://www.xmms.org/>
871 * libyajl (optional)
872 Parse JSON data. This is needed for the `ceph', `curl_json' and
873 `log_logstash' plugins.
874 <http://github.com/lloyd/yajl>
876 * libvarnish (optional)
877 Fetches statistics from a Varnish instance. This is needed for the
878 `varnish' plugin.
879 <http://varnish-cache.org>
881 * riemann-c-client (optional)
882 For the `write_riemann' plugin.
883 <https://github.com/algernon/riemann-c-client>
885 Configuring / Compiling / Installing
886 ------------------------------------
888 To configure, build and install collectd with the default settings, run
889 `./configure && make && make install'. For detailed, generic instructions
890 see INSTALL. For a complete list of configure options and their description,
891 run `./configure --help'.
893 By default, the configure script will check for all build dependencies and
894 disable all plugins whose requirements cannot be fulfilled (any other plugin
895 will be enabled). To enable a plugin, install missing dependencies (see
896 section `Prerequisites' above) and rerun `configure'. If you specify the
897 `--enable-<plugin>' configure option, the script will fail if the depen-
898 dencies for the specified plugin are not met. In that case you can force the
899 plugin to be built using the `--enable-<plugin>=force' configure option.
900 This will most likely fail though unless you're working in a very unusual
901 setup and you really know what you're doing. If you specify the
902 `--disable-<plugin>' configure option, the plugin will not be built. If you
903 specify the `--enable-all-plugins' or `--disable-all-plugins' configure
904 options, all plugins will be enabled or disabled respectively by default.
905 Explicitly enabling or disabling a plugin overwrites the default for the
906 specified plugin. These options are meant for package maintainers and should
907 not be used in everyday situations.
909 By default, collectd will be installed into `/opt/collectd'. You can adjust
910 this setting by specifying the `--prefix' configure option - see INSTALL for
911 details. If you pass DESTDIR=<path> to `make install', <path> will be
912 prefixed to all installation directories. This might be useful when creating
913 packages for collectd.
915 Configuring with libjvm
916 -----------------------
918 To determine the location of the required files of a Java installation is not
919 an easy task, because the locations vary with your kernel (Linux, SunOS, …)
920 and with your architecture (x86, SPARC, …) and there is no ‘java-config’
921 script we could use. Configuration of the JVM library is therefore a bit
922 tricky.
924 The easiest way to use the `--with-java=$JAVA_HOME' option, where
925 `$JAVA_HOME' is usually something like:
926 /usr/lib/jvm/java-1.5.0-sun-1.5.0.14
928 The configure script will then use find(1) to look for the following files:
930 - jni.h
931 - jni_md.h
932 - libjvm.so
934 If found, appropriate CPP-flags and LD-flags are set and the following
935 library checks succeed.
937 If this doesn't work for you, you have the possibility to specify CPP-flags,
938 C-flags, LD-flags and LIBS for the ‘Java’ plugin by hand, using the
939 following environment variables:
941 - JAVA_CPPFLAGS
942 - JAVA_CFLAGS
943 - JAVA_LDFLAGS
944 - JAVA_LIBS
946 For example (shortened for demonstration purposes):
948 ./configure JAVA_CPPFLAGS="-I$JAVA_HOME/include -I$JAVA_HOME/include/linux"
950 Adding "-ljvm" to JAVA_LIBS is done automatically, you don't have to
951 do that.
953 Generating the configure script
954 -------------------------------
956 Collectd ships with a `build.sh' script to generate the `configure'
957 script shipped with releases.
959 To generate the `configure` script, you'll need the following dependencies:
961 - autoconf
962 - automake
963 - flex
964 - bison
965 - libtool
966 - libtool-ltdl
967 - pkg-config
969 The `build.sh' script takes no arguments.
971 Crosscompiling
972 --------------
974 To compile correctly collectd needs to be able to initialize static
975 variables to NAN (Not A Number). Some C libraries, especially the GNU
976 libc, have a problem with that.
978 Luckily, with GCC it's possible to work around that problem: One can define
979 NAN as being (0.0 / 0.0) and `isnan' as `f != f'. However, to test this
980 ``implementation'' the configure script needs to compile and run a short
981 test program. Obviously running a test program when doing a cross-
982 compilation is, well, challenging.
984 If you run into this problem, you can use the `--with-nan-emulation'
985 configure option to force the use of this implementation. We can't promise
986 that the compiled binary actually behaves as it should, but since NANs
987 are likely never passed to the libm you have a good chance to be lucky.
989 Likewise, collectd needs to know the layout of doubles in memory, in order
990 to craft uniform network packets over different architectures. For this, it
991 needs to know how to convert doubles into the memory layout used by x86. The
992 configure script tries to figure this out by compiling and running a few
993 small test programs. This is of course not possible when cross-compiling.
994 You can use the `--with-fp-layout' option to tell the configure script which
995 conversion method to assume. Valid arguments are:
997 * `nothing' (12345678 -> 12345678)
998 * `endianflip' (12345678 -> 87654321)
999 * `intswap' (12345678 -> 56781234)
1002 Contact
1003 -------
1005 For questions, bug reports, development information and basically all other
1006 concerns please send an email to collectd's mailing list at
1007 <list at collectd.org>.
1009 For live discussion and more personal contact visit us in IRC, we're in
1010 channel #collectd on freenode.
1013 Author
1014 ------
1016 Florian octo Forster <octo at collectd.org>,
1017 Sebastian tokkee Harl <sh at tokkee.org>,
1018 and many contributors (see `AUTHORS').
1020 Please use GitHub reporting bugs and submitting pull requests.
1021 See CONTRIBUTING.md for details.