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 Number of nf_conntrack entries.
61 Number of context switches done by the operating system.
64 CPU utilization: Time spent in the system, user, nice, idle, and related
68 CPU frequency (For laptops with speed step or a similar technology)
71 CPU sleep: Time spent in suspend (For mobile devices which enter suspend automatically)
74 Parse statistics from websites using regular expressions.
77 Retrieves JSON data via cURL and parses it according to user
81 Retrieves XML data via cURL and parses it according to user
85 Executes SQL statements on various databases and interprets the returned
89 Mountpoint usage (Basically the values `df(1)' delivers)
92 Disk utilization: Sectors read/written, number of read/write actions,
93 average time an IO-operation took to complete.
96 DNS traffic: Query types, response codes, opcodes and traffic/octets
100 Collect individual drbd resource statistics.
103 Email statistics: Count, traffic, spam scores and checks.
104 See collectd-email(5).
107 Amount of entropy available to the system.
110 Network interface card statistics.
113 Values gathered by a custom program or script.
114 See collectd-exec(5).
117 File handles statistics.
120 Count the number of files in directories.
123 Linux file-system based caching framework statistics.
126 Receive multicast traffic from Ganglia instances.
129 Monitor gps related data through gpsd.
132 Receive values over the network using the gRPC framework.
135 Hard disk temperatures using hddtempd.
138 Interface traffic: Number of octets, packets and errors for each
142 IPC counters: semaphores used, number of allocated segments in shared
146 IPMI (Intelligent Platform Management Interface) sensors information.
149 Iptables' counters: Number of bytes that were matched by a certain
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.
158 IRQ counters: Frequency in which certain interrupts occur.
161 Integrates a `Java Virtual Machine' (JVM) to execute plugins in Java
162 bytecode. See “Configuring with libjvm” below.
165 System load average over the last 1, 5 and 15 minutes.
168 Detailed CPU statistics of the “Logical Partitions” virtualization
169 technique built into IBM's POWER processors.
172 Size of “Logical Volumes” (LV) and “Volume Groups” (VG) of Linux'
173 “Logical Volume Manager” (LVM).
176 Queries very detailed usage statistics from wireless LAN adapters and
177 interfaces that use the Atheros chipset and the MadWifi driver.
180 Motherboard sensors: temperature, fan speed and voltage information,
184 Linux software-RAID device information (number of active, failed, spare
188 Query and parse data from a memcache daemon (memcached).
191 Statistics of the memcached distributed caching system.
192 <http://www.danga.com/memcached/>
195 Memory utilization: Memory occupied by running processes, page cache,
196 buffer cache and free.
199 Collects CPU usage, memory usage, temperatures and power consumption from
200 Intel Many Integrated Core (MIC) CPUs.
203 Reads values from Modbus/TCP enabled devices. Supports reading values
204 from multiple "slaves" so gateway devices can be used.
207 Publishes and subscribes to MQTT topics.
210 Information provided by serial multimeters, such as the `Metex
214 MySQL server statistics: Commands issued, handlers triggered, thread
215 usage, query cache utilization and traffic/octets sent and received.
218 Plugin to query performance values from a NetApp storage system using the
219 “Manage ONTAP” SDK provided by NetApp.
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.
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.
232 NFS Procedures: Which NFS command were called how often. Only NFSv2 and
236 Collects statistics from `nginx' (speak: engine X), a HTTP and mail
240 NTP daemon statistics: Local clock drift, offset to peers, etc.
243 Information about Non-Uniform Memory Access (NUMA).
246 Network UPS tools: UPS current, voltage, power, charge, utilisation,
247 temperature, etc. See upsd(8).
250 Queries routing information from the “Optimized Link State Routing”
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.
258 Read monitoring information from OpenLDAP's cn=Monitor subtree.
261 RX and TX of each client in openvpn-status.log (status-version 2).
262 <http://openvpn.net/index.php/documentation/howto.html>
265 Query data from an Oracle database.
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).
273 Query statistics from BSD's packet filter "pf".
276 Receive and dispatch timing values from Pinba, a profiling extension for
280 Network latency: Time to reach the default gateway or another given
284 PostgreSQL database statistics: active server connections, transaction
285 numbers, block IO, table row manipulations.
288 PowerDNS name server statistics.
291 Process counts: Number of running, sleeping, zombie, ... processes.
294 Counts various aspects of network protocols such as IP, TCP, UDP, etc.
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.
303 The redis plugin gathers information from a Redis server, including:
304 uptime, used memory, total connections etc.
307 Query interface and wireless registration statistics from RouterOS.
310 RRDtool caching daemon (RRDcacheD) statistics.
313 System sensors, accessed using lm_sensors: Voltages, temperatures and
317 RX and TX of serial interfaces. Linux only; needs root privileges.
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.
325 Collect SMART statistics, notably load cycle count, temperature
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).
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.
338 Pages swapped out onto hard disk or whatever is called `swap' by the OS..
341 Parse table-like structured files.
344 Follows (tails) log files, parses them by lines and submits matched
348 Follows (tails) files in CSV format, parses each line and submits
352 Bytes and operations read and written on tape devices. Solaris only.
355 Number of TCP connections to specific local and remote ports.
358 TeamSpeak2 server statistics.
361 Plugin to read values from `The Energy Detective' (TED).
364 Linux ACPI thermal zone information.
367 Reads the number of records and file size from a running Tokyo Tyrant
371 Reads CPU frequency and C-state residency on modern Intel
372 turbo-capable processors.
375 System uptime statistics.
378 Users currently logged in.
381 Various statistics from Varnish, an HTTP accelerator.
384 CPU, memory, disk and network I/O statistics from virtual machines.
387 Virtual memory statistics, e. g. the number of page-ins/-outs or the
388 number of pagefaults.
391 System resources used by Linux VServers.
392 See <http://linux-vserver.org/>.
395 Link quality of wireless cards. Linux only.
398 XEN Hypervisor CPU stats.
401 Bitrate and frequency of music played with XMMS.
404 Statistics for ZFS' “Adaptive Replacement Cache” (ARC).
407 Measures the percentage of cpu load per container (zone) under Solaris 10
411 Read data from Zookeeper's MNTR command.
413 * Output can be written or sent to various destinations by the following
417 Sends JSON-encoded data to an Advanced Message Queuing Protocol (AMQP)
418 server, such as RabbitMQ.
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..
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.
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).
435 It's possible to implement write plugins in Python using the python
436 plugin. See collectd-python(5) for details.
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.
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
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
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
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.
466 Sends data to Apache Kafka, a distributed queue.
469 Writes data to the log
472 Sends data to MongoDB, a NoSQL database.
475 Sends the values to a Redis key-value database server.
478 Sends data to Riemann, a stream processing and monitoring system.
481 Sends data to Sensu, a stream processing and monitoring system, via the
482 Sensu client local TCP socket.
485 Sends data OpenTSDB, a scalable no master, no shared state time series
488 * Logging is, as everything in collectd, provided by plugins. The following
489 plugins keep us informed about what's going on:
492 Writes log messages to a file or STDOUT/STDERR.
495 Log messages are propagated to plugins written in Perl as well.
496 See collectd-perl(5).
499 It's possible to implement log plugins in Python using the python plugin.
500 See collectd-python(5) for details.
503 Logs to the standard UNIX logging mechanism, syslog.
506 Writes log messages formatted as logstash JSON events.
508 * Notifications can be handled by the following plugins:
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/.
517 Send an E-mail with the notification message to the configured
521 Submit notifications as passive check results to a local nagios instance.
524 Execute a program or script to handle the notification.
525 See collectd-exec(5).
528 Writes the notification message to a file or STDOUT/STDERR.
531 Send the notification to a remote host to handle it somehow.
534 Notifications are propagated to plugins written in Perl as well.
535 See collectd-perl(5).
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.
548 Match values using a hash function of the hostname.
551 Match values by their identifier based on regular expressions.
554 Match values with an invalid timestamp.
557 Select values by their data sources' values.
559 - target_notification
560 Create and dispatch a notification.
563 Replace parts of an identifier using regular expressions.
566 Scale (multiply) values by an arbitrary value.
569 Set (overwrite) entire parts of an identifier.
571 * Miscellaneous plugins:
574 Selects multiple value lists based on patterns or regular expressions
575 and creates new aggregated values lists from those.
578 Checks values against configured thresholds and creates notifications if
579 values are out of bounds. See collectd-threshold(5) for details.
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.
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.
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
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'
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
661 <http://developer.apple.com/corefoundation/>
663 * libatasmart (optional)
664 Used by the `smart' plugin.
665 <http://git.0pointer.de/?p=libatasmart.git>
668 The `turbostat' plugin can optionally build Linux Capabilities support,
669 which avoids full privileges requirement (aka. running as root) to read
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>
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/>
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/>
698 Used by the `grpc' plugin. gRPC requires a C++ compiler supporting the
702 * libgcrypt (optional)
703 Used by the `network' plugin for encryption and authentication.
704 <http://www.gnupg.org/>
707 Used by the `gps' plugin.
708 <http://developer.berlios.de/projects/gpsd/>
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.
719 For querying iptables counters.
720 <http://netfilter.org/>
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
726 <http://openjdk.java.net/> (and others)
729 Used by the `openldap' plugin.
730 <http://www.openldap.org/>
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>
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
777 <http://www.owfs.org/>
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.
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/>
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
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
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/>
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
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/>
856 Collect statistics from virtual machines.
857 <http://libvirt.org/>
860 Parse XML data. This is needed for the `ascent', `bind', `curl_xml' and
862 <http://xmlsoft.org/>
865 Used by the `xencpu' plugin.
866 <http://xenbits.xensource.com/>
869 <http://www.xmms.org/>
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
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
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:
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:
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
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:
969 The `build.sh' script takes no arguments.
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)
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.
1016 Florian octo Forster <octo at collectd.org>,
1017 Sebastian tokkee Harl <sh at tokkee.org>,
1018 and many contributors (see `AUTHORS').
1020 Please send bug reports and patches to the mailing list, see `Contact'
projects / collectd.git / blob