+ - 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
+ M-4650CR'.
+
+ - 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 arbitrary 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
+ host.
+
+ - 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 resources used by Linux VServers.
+ See <http://linux-vserver.org/>.
+
+ - wireless
+ Link quality of wireless cards. Linux only.
+
+ * Output can be written or send to various destinations by the following
+ plugins:
+
+ - csv
+ Write to comma separated 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
+ done.
+
+ * 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 mechanism, 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 maintenance is necessary. Setup is kept as easy
+ as possible and the default values should be okay for most users.