Skip to content
Mirror of the official repository.
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


 collectd - System information collection daemon


  collectd is a small daemon which collects statistics about a computer's
  usage and writes then into RRD files.


  * collectd is able to collect the following data:

    - apache
      Apache server utilization: Number of bytes transfered, number of
      requests handled and detailed scoreboard statistics

    - apcups
      APC UPS Daemon: UPS charge, load, input/output/battery voltage, etc.

    - apple_sensors
      Sensors in Macs running Mac OS X / Darwin: Temperature, fanspeed and
      voltage sensors.

    - battery
      Batterycharge, -current and volatage of ACPI and PMU based laptop

    - cpu
      CPU utilization: Time spent in the system, user, nice, idle, and related

    - cpufreq
      CPU frequency (For laptops with speed step or a similar technology)

    - df
      Mountpoint usage (Basically the values `df(1)' delivers)

    - disk
      Disk utilization: Sectors read/written, number of read/write actions,
      average time an IO-operation took to complete.

    - dns
      DNS traffic: Query types, response codes, opcodes and traffic/octets

    - email
      Email statistics: Count, traffic, spam scores and checks.
      See collectd-email(5).

    - entropy
      Amount of entropy available to the system.

    - exec
      Values gathered by a custom program or script.
      See collectd-exec(5).

    - hddtemp
      Harddisk temperatures using hddtempd.

    - interface
      Interface traffic: Number of octets, packets and errors for each

    - iptables
      Iptables' counters: Number of bytes that were matched by a certain
      iptables rule.

    - irq
      IRQ counters: Frequency in which certain interrupts occur.

    - load
      System load average over the last 1, 5 and 15 minutes.

    - mbmon
      Motherboard sensors: temperature, fanspeed and voltage information,
      using mbmon(1).

    - memory
      Memory utilization: Memory occupied by running processes, page cache,
      buffer cache and free.

    - multimeter
      Information provided by serial multimeters, such as the `Metex

    - mysql
      MySQL server statistics: Commands issued, handlers triggered, thread
      usage, query cache utilization and traffic/octets sent and received.

    - network
      Receive values that were collected by other hosts. Large setups will
      want to collect the data on one dedicated machine, and this is the
      plugin of choice for that.

    - nfs
      NFS Procedures: Which NFS command were called how often. Only NFSv2 and
      NFSv3 right now.

    - ntp
      NTP daemon statistics: Local clock drift, offset to peers, etc.

    - nut
      Network UPS tools: UPS current, voltage, power, charge, utilisation,
      temperature, etc. See upsd(8).

    - perl
      The perl plugin implements a Perl-interpreter into collectd. You can
      write your own plugins in Perl and return arbitary values using this
      API. See collectd-perl(5).

      This plugin is still considered to be experimental and subject to change
      between minor releases.

    - ping
      Network latency: Time to reach the default gateway or another given

    - processes
      Process counts: Number of running, sleeping, zombie, ... processes.

    - sensors
      System sensors, accessed using lm_sensors: Voltages, temperatures and
      fan rotation speeds.

    - serial
      RX and TX of serial interfaces. Linux only; needs root privileges.

    - swap
      Pages swapped out onto harddisk or whatever is called `swap' by the OS..

    - tape
      Bytes and operations read and written on tape devices. Solaris only.

    - users
      Users currently logged in.

    - vserver
      System ressources used by Linux VServers.
      See <>.

    - wireless
      Link quality of wireless cards. Linux only.

  * Output can be written or send to various destinations by the following

    - csv
      Write to comma seperated values (CSV) files. This needs lots of
      diskspace but is extremely portable and can be analysed with almost
      every program that can analyse anything. Even Microsoft's Excel..

    - network
      Send the data to a remote host to save the data somehow. This is useful
      for large setups where the data should be saved by a dedicated machine.

    - perl
      Of course the values are propagated to plugins written in Perl, too, so
      you can easily do weird stuff with the plugins we didn't dare think of
      ;) See collectd-perl(5).

    - rrdtool
      Output to round-robin-database (RRD) files using librrd. See rrdtool(1).
      This is likely the most popular destination for such values. Since
      updates to RRD-files are somewhat expensive this plugin can cache
      updates to the files and write a bunch of updates at once, which lessens
      system load a lot.

    - unixsock
      One can query the values from the unixsock plugin whenever they're
      needed. Please read collectd-unixsock(5) for a description on how that's

  * Logging is, as everything in collectd, provided by plugins. The following
    plugins keep up informed about what's going on:

    - logfile
      Writes logmessages to a file or STDOUT/STDERR.

    - syslog
      Logs to the standard UNIX logging mechanismn, syslog.

  * Performance: Since collectd is running as a daemon it doesn't spend much
    time starting up again and again. With the exception of the exec plugin no
    processes are forked. Caching in output plugins, such as the rrdtool and
    network plugins, makes sure your resources are used efficiently. Also,
    since collectd is programmed multithreaded it benefits from hyperthreading
    and multicore processors and makes sure that the daemon isn't idle if only
    one plugins waits for an IO-operation to complete.
  * Once set up, hardly any maintenence is neccessary. Setup is kept as easy
    as possible and the default values should be okay for most users.


  * collectd's configuration file can be found at `sysconfdir'/collectd.conf.
    Run `collectd -h' for a list of builtin defaults. See `collectd.conf(5)'
    for a list of options and a syntax description.

  * When the `csv' or `rrdtool' plugins are loaded they'll write the values to
    files. The usual place for these files is beneath `/var/lib/collectd'.

  * When using some of the plugins, collectd needs to run as user root, since only
    root can do certain things, such as craft ICMP packages needed to ping
    other hosts. collectd should NOT be installed setuid root since it can be
    used to overwrite valuable files!

  * Sample scripts to generate graphs reside in `contrib/' in the source
    package or somewhere near `/usr/share/doc/collectd' in most distributions.
    Please be aware that those script are meant as a starting point for your
    own experiments.. Some of them require the `RRDs' Perl module.
    (`librrds-perl' on Debian) If you have written a more sophisticated
    solution please share it with us.

  * The RRAs of the automatically created RRD files depend on the `step'
    and `heartbeat' settings given. If change these settings you may need to
    re-create the files, losing all data. Please be aware of that when changing
    the values and read the rrdtool(1) manpage thoroughly.


  To compile collectd from source you will need:

  * Usual suspects: C compiler, linker, preprocessor, make, ...

  * A POSIX-threads (pthread) implementation.
    Since gathering some statistics is slow (network connections, slow devices,
    etc) the collectd is parellelized. The POSIX threads interface is being
    used and should be found in various implementations for hopefully all

  * libcurl (optional)
    If you want to use the `apache' plugin

  * libiptc (optional)
    For querying iptables counters.

  * libmysqlclient (optional)

  * liboping (optional, if not found a version shipped with this distribution
    can be used)
    Used by the `ping' plugin to send and receive ICMP packets.

  * libpcap (optional)
    Used to capture packets by the `dns' plugin.

  * librrd (optional; headers and library; rrdtool 1.0 and 1.2 both work fine)
    If built without `librrd' the resulting binary will be `client only', i.e.
    will send its values via multicast and not create any RRD files itself.
    Alternatively you can chose to write CSV-files (Comma Seperated Values)

  * libsensors (optional)
    To read from `lm_sensors'.

  * libstatgrab may be used to collect statistics on systems other than Linux
    and/or Solaris. Note that CPU- and disk-statistics, while being provided
    by this library, are not supported in collectd right now..

  * libupsclient/nut (optional)
    For the `nut' plugin which queries nut's `upsd'.

  * librt, libsocket, libkstat, libdevinfo
    Various standard Solaris libraries which provide system functions.

  * CoreFoundation.framework and IOKit.framework
    For compiling on Darwin in general and the `apple_sensors' plugin in


    To compile correctly collectd needs to be able to initialize static
    variables to NAN (Not A Number). Some C libraries, especially the GNU
    libc, have a problem with that.

    Luckily, with GCC it's possible to work around that problem: One can define
    NAN as being (0.0 / 0.0) and `isnan' as `f != f'. However, to test this
    ``implementation'' the configure script needs to compile and run a short
    test program. Obviously running a test program when doing a cross-
    compilation is, well, challenging.

    If you run into this problem, you can use the `--with-nan-emulation'
    configure option to force the use of this implementation. We can't promise
    that the compiled binary actually behaves as it should, but since NANs
    are likely never passed to the libm you have a good chance to be lucky.


  Florian octo Forster <octo at>,
  Sebastian tokkee Harl <sh at>,
  and many contributors (see `AUTHORS').

Something went wrong with that request. Please try again.