Iptables' counters: Number of bytes that were matched by a certain
iptables rule.
+ - ipvs
+ IPVS connection statistics (number of connections, octets and packets
+ for each service and destination).
+ See http://www.linuxvirtualserver.org/software/index.html.
+
- irq
IRQ counters: Frequency in which certain interrupts occur.
Motherboard sensors: temperature, fanspeed and voltage information,
using mbmon(1).
+ - memcached
+ Statistics of the memcached distributed caching system.
+ <http://www.danga.com/memcached/>
+
- memory
Memory utilization: Memory occupied by running processes, page cache,
buffer cache and free.
MySQL server statistics: Commands issued, handlers triggered, thread
usage, query cache utilization and traffic/octets sent and received.
+ - netlink
+ Very detailed Linux network interface and routing statistics. You can get
+ (detailed) information on interfaces, qdiscs, classes, and, if you can
+ make use of it, filters.
+
- 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
NFS Procedures: Which NFS command were called how often. Only NFSv2 and
NFSv3 right now.
+ - nginx
+ Collects statistics from `nginx' (speak: engine X), a HTTP and mail
+ server/proxy.
+
- ntp
NTP daemon statistics: Local clock drift, offset to peers, etc.
- serial
RX and TX of serial interfaces. Linux only; needs root privileges.
+ - snmp
+ Read values from SNMP (Simple Network Management Protocol) enabled
+ network devices such as switches, routers, thermometers, rack monitoring
+ servers, etc. See collectd-snmp(5).
+
- 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.
+ - tcpconns
+ Number of TCP connections to specific local and remote ports.
+
- users
Users currently logged in.
- wireless
Link quality of wireless cards. Linux only.
+ - xmms
+ Bitrate and frequency of music played with XMMS.
+
* Output can be written or send to various destinations by the following
plugins:
* 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
+ * 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!
the values and read the rrdtool(1) manpage thoroughly.
+collectd and chkrootkit
+-----------------------
+
+ If you are using the `dns' plugin chkrootkit(1) will report collectd as a
+ packet sniffer ("<iface>: PACKET SNIFFER(/usr/sbin/collectd[<pid>])"). The
+ plugin captures all UDP packets on port 53 to analyze the DNS traffic. In
+ this case, collectd is a legitimate sniffer and the report should be
+ considered to be a false positive. However, you might want to check that
+ this really is collectd and not some other, illegitimate sniffer.
+
+
Prerequisites
-------------
* libmysqlclient (optional)
+ * libnetlink (optional)
+
+ * libnetsnmp (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.
* libupsclient/nut (optional)
For the `nut' plugin which queries nut's `upsd'.
+ * libxmms (optional)
+
* librt, libsocket, libkstat, libdevinfo
Various standard Solaris libraries which provide system functions.
Crosscompiling
--------------
- 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.
+ 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.
+ 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.
+ 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.
Contact
projects / collectd.git / blobdiff