X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=src%2Fcollectd.pod;h=2f7b9f707439c795fcf85acfaede29ec39821a2e;hb=a186ae0e1c37db7baa356d99278576d8176f7c1c;hp=5c30558cc890ac32724379c0e35af7a4b097096e;hpb=c87194194948fec81eb7ead8b7d9615efc7778e1;p=collectd.git diff --git a/src/collectd.pod b/src/collectd.pod index 5c30558c..2f7b9f70 100644 --- a/src/collectd.pod +++ b/src/collectd.pod @@ -1,3 +1,5 @@ +=encoding UTF-8 + =head1 NAME collectd - System statistics collection daemon @@ -8,101 +10,46 @@ collectd I<[options]> =head1 DESCRIPTION -collectd is a daemon that collects various system statistics periodically and -stores them into RRD-files. Which data is collected depends on compile-time -settings. The following features may be available: - -=over 4 - -=item - -Battery status (I) - -=item - -CPU utilization (I) - -=item - -Mountpoint usage (I) - -=item - -Disk and partition usage/throughput (I) - -=item - -Harddisk temperatures (I) - -=item - -System load averages (I) - -=item - -Memory usage (I) - -=item - -MySQL statistics (I) - -=item - -NFS utilization (I, Linux only) - -=item - -Network latency (I) - -=item - -Number of processes (I, Linux only) - -=item - -lm_sensors information (I, Linux only) - -=item - -Serial port traffic (I, Linux only) - -=item - -Swap usage (I) - -=item - -Tape drive usage (I, Solaris only) +collectd is a daemon that receives system statistics and makes them available +in a number of ways. The main daemon itself doesn't have any real functionality +apart from loading, querying and submitting to plugins. For a description of +available plugins please see L below. -=item +=head1 OPTIONS -Network traffic (I) +Most of collectd's configuration is done using using a configfile. See +L for an in-depth description of all options. -=item +=over 4 -Number of users logged into the system (I) +=item B<-C> Iconfig-fileE> -=item +Specify an alternative config file. This is the place to go when you wish to +change B's behavior. The path may be relative to the current working +directory. -System ressources used by VServers (I) +=item B<-t> -=back +Test the configuration only. The program immediately exits after parsing the +config file. A return code not equal to zero indicates an error. -=head1 OPTIONS +=item B<-T> -=over 4 +Test the plugin read callbacks only. The program immediately exits after invoking +the read callbacks once. A return code not equal to zero indicates an error. -=item B<-C> Iconfig-fileE> +=item B<-P> Ipid-fileE> -Specify an alternative config file. This is the place to go when you wish to -change B's behavior. The path may be relative to the current working -directory. +Specify an alternative pid file. This overwrites any settings in the config +file. This is thought for init-scripts that require the PID-file in a certain +directory to work correctly. For everyday-usage use the B +config-option. =item B<-f> Don't fork to the background. I will also B close standard file descriptors, detach from the session nor write a pid file. This is mainly -thought for 'supervisioning' init replacements such as I. +thought for 'supervising' init replacements such as I. =item B<-h> @@ -110,324 +57,84 @@ Output usage information and exit. =back -=head1 MODES +=head1 PLUGINS -collectd can operate in three different operating modes. The modes are -described below. +As noted above, the real power of collectd lies within it's plugins. A +(hopefully complete) list of plugins and short descriptions can be found in the +F file that is distributed with the sourcecode. If you're using a +package it's a good bet to search somewhere near F. -The simplest mode is the so called B. Data is collected locally and -written in RRD files that reside in I. This is the default mode when -collectd is linked against C. - -The other two modes, B and B, are used to send data -over a network and receive it again. - -In B the daemon collects the data locally and sends it's results -to one or more network addresses. No RRD files are written in this case. This -is the only mode available if collectd is not linked against C. - -If started in B the daemon will listen on one or more interfaces -and write the data it receives to RRD files. No data is collected locally. - -Please refer to L for the configuration options and default -values. - -=head1 SPECIAL PLUGINS - -=head2 cpufreq - -This module reads F (for -the first CPU installed) to get the current CPU frequency. If this file does -not exist make sure B (L) or a -similar tool is installed. - -=head2 mysql - -Requires B to be installed. It connects to the database when -started and keeps the connection up as long as possible. When the connection is -interrupted for whatever reason it will try to re-connect. The syslog will -contain loud complaints in case anything goes wrong. - -This plugin issues C and evaluates C, -C and C which correspond to F, -F and F. Also, the values of -C are put in F and values of C are put -in F. Please refer to the B, -I<5.2.4. Server Status Variables> for an explanation of these values. - -=head2 sensors - -The B module uses lm_sensors to retrieve sensor-values. This means -that all the needed modules have to be loaded and lm_sensors has to be -configured (most likely by editing F. Read -L for details. - -The B homepage can be found at -L. - -=head2 hddtemp - -To get values from B collectd connects to B (127.0.0.1), -port B<7634/tcp>. The B and B options can be used to change these -default values. See L for details. C has to be -running to work correctly. If C is not running timeouts may appear -which may interfere with other statistics.. - -The B homepage can be found at -L. - -=head2 vserver - -B support is only available for Linux. It cannot yet be found in a -vanilla kernel, though. To make use of this plugin you need a kernel that has -B support built in, i.e. you need to apply the patches and compile -your own kernel, which will then provide the /proc/virtual filesystem that is -required by this plugin. - -The B homepage can be found at L. - -=head1 RRD FILES - -The RRD files are created automatically with the following RRAs: - - RRA:AVERAGE:0.0:1:1500 - RRA:AVERAGE:0.2:6:1500 - RRA:AVERAGE:0.1:180:1680 - RRA:AVERAGE:0.1:2160:1520 - RRA:MIN:0.0:1:1500 - RRA:MIN:0.2:6:1500 - RRA:MIN:0.1:180:1680 - RRA:MIN:0.1:2160:1520 - RRA:MAX:0.0:1:1500 - RRA:MAX:0.2:6:1500 - RRA:MAX:0.1:180:1680 - RRA:MAX:0.1:2160:1520 - -By default collectd uses a 10 second I. Thus the RRAs contain the -following timespans. If you've changed the I at compile time you will -have calculate resolution and timespan yourself. - - PDP per CDP | Resolution | Data points | Timespan - ------------+------------+-------------+---------- - 1 | 10 seconds ! 1500 ! 4 hours - 6 | 1 minute | 1500 | 25 hours - 180 | 30 minutes | 1680 | 35 days - 2160 | 6 hours | 1520 | 380 days - -The DS'es depend on the module creating the RRD files: +There are two big groups of plugins, B and B plugins: =over 4 -=item Battery charge (FnameE>/charge.rrd>) - - DS:charge:GAUGE:25:0:U - -=item Battery current (FnameE>/current.rrd>) - - DS:current:GAUGE:25:U:U - -=item Battery voltage (FnameE>/voltage.rrd>) - - DS:voltage:GAUGE:25:U:U - -=item CPU (FnumE>.rrd>) - - DS:user:COUNTER:25:0:100 - DS:nice:COUNTER:25:0:100 - DS:syst:COUNTER:25:0:100 - DS:idle:COUNTER:25:0:100 - DS:wait:COUNTER:25:0:100 - -=item Mountpoints (FpathE>.rrd>) - - DS:used:GAUGE:25:0:U - DS:free:GAUGE:25:0:U - -=item Diskstats (FmajorE>-IminorE>.rrd>) - - DS:rcount:COUNTER:25:0:U - DS:rmerged:COUNTER:25:0:U - DS:rbytes:COUNTER:25:0:U - DS:rtime:COUNTER:25:0:U - DS:wcount:COUNTER:25:0:U - DS:wmerged:COUNTER:25:0:U - DS:wbytes:COUNTER:25:0:U - DS:wtime:COUNTER:25:0:U - -=item Diskstats (FmajorE>-IminorE>.rrd>) - - DS:rcount:COUNTER:25:0:U - DS:rbytes:COUNTER:25:0:U - DS:wcount:COUNTER:25:0:U - DS:wbytes:COUNTER:25:0:U - -=item HDD Temperature (FmajorE>-IminorE>.rrd>) - - DS:value:GAUGE:25:U:U - -=item System load (F) - - DS:shortterm:GAUGE:25:0:100 - DS:midterm:GAUGE:25:0:100 - DS:longterm:GAUGE:25:0:100 - -=item Memory usage (F) - - DS:used:GAUGE:25:0:9223372036854775807 - DS:free:GAUGE:25:0:9223372036854775807 - DS:buffers:GAUGE:25:0:9223372036854775807 - DS:cached:GAUGE:25:0:9223372036854775807 - -=item MySQL commands and handlers (FcommandE>.rrd> and FhandlerE>.rrd>) - - DS:value:COUNTER:25:0:U - -=item MySQL query cache (F) - - DS:hits:COUNTER:25:0:U - DS:inserts:COUNTER:25:0:U - DS:not_cached:COUNTER:25:0:U - DS:lowmem_prunes:COUNTER:25:0:U - DS:queries_in_cache:GAUGE:25:0:U - -=item MySQL threads (F) - - DS:running:GAUGE:25:0:U - DS:connected:GAUGE:25:0:U - DS:cached:GAUGE:25:0:U - DS:created:COUNTER:25:0:U - -=item NFSv2 Procedures (F.rrd>) - - DS:null:COUNTER:25:0:U - DS:getattr:COUNTER:25:0:U - DS:setattr:COUNTER:25:0:U - DS:root:COUNTER:25:0:U - DS:lookup:COUNTER:25:0:U - DS:readlink:COUNTER:25:0:U - DS:read:COUNTER:25:0:U - DS:wrcache:COUNTER:25:0:U - DS:write:COUNTER:25:0:U - DS:create:COUNTER:25:0:U - DS:remove:COUNTER:25:0:U - DS:rename:COUNTER:25:0:U - DS:link:COUNTER:25:0:U - DS:symlink:COUNTER:25:0:U - DS:mkdir:COUNTER:25:0:U - DS:rmdir:COUNTER:25:0:U - DS:readdir:COUNTER:25:0:U - DS:fsstat:COUNTER:25:0:U - -=item NFSv3 Procedures (F.rrd>) - - DS:null:COUNTER:25:0:U - DS:getattr:COUNTER:25:0:U - DS:setattr:COUNTER:25:0:U - DS:lookup:COUNTER:25:0:U - DS:access:COUNTER:25:0:U - DS:readlink:COUNTER:25:0:U - DS:read:COUNTER:25:0:U - DS:write:COUNTER:25:0:U - DS:create:COUNTER:25:0:U - DS:mkdir:COUNTER:25:0:U - DS:symlink:COUNTER:25:0:U - DS:mknod:COUNTER:25:0:U - DS:remove:COUNTER:25:0:U - DS:rmdir:COUNTER:25:0:U - DS:rename:COUNTER:25:0:U - DS:link:COUNTER:25:0:U - DS:readdir:COUNTER:25:0:U - DS:readdirplus:COUNTER:25:0:U - DS:fsstat:COUNTER:25:0:U - DS:fsinfo:COUNTER:25:0:U - DS:pathconf:COUNTER:25:0:U - DS:commit:COUNTER:25:0:U - -=item Network latency / Ping (FhostnameE>.rrd>) - - DS:ping:GAUGE:25:0:65535 - -=item Processes (F) - - DS:running:GAUGE:25:0:65535 - DS:sleeping:GAUGE:25:0:65535 - DS:zombies:GAUGE:25:0:65535 - DS:stopped:GAUGE:25:0:65535 - DS:paging:GAUGE:25:0:65535 - DS:blocked:GAUGE:25:0:65535 - -=item lm_sensors (FchipE>-IfeatureE>.rrd>) - - DS:value:GAUGE:25:U:U +=item -=item Serial port traffic (FnumE>.rrd>) +Input plugins are queried periodically. They somehow acquire the current value +of whatever they where designed to work with and submit these values back to +the daemon, i. e. they "dispatch" the values. As an example, the C +reads the current cpu-counters of time spent in the various modes (user, +system, nice, ...) and dispatches these counters to the daemon. - DS:incoming:COUNTER:25:0:U - DS:outgoing:COUNTER:25:0:U +=item -=item Swap usage (F) +Output plugins get the dispatched values from the daemon and does something +with them. Common applications are writing to RRD-files, CSV-files or sending +the data over a network link to a remote box. - DS:used:GAUGE:25:0:1099511627776 - DS:free:GAUGE:25:0:1099511627776 - DS:cached:GAUGE:25:0:1099511627776 - DS:resv:GAUGE:25:0:1099511627776 +=back -=item Tape drive usage (FnameE>.rrd>) +Of course not all plugins fit neatly into one of the two above categories. The +C, for example, is able to send (i.Ee. "write") B +receive (i.Ee. "dispatch") values. Also, it opens a socket upon +initialization and dispatches the values when it receives them and isn't +triggered at the same time the input plugins are being read. You can think of +the network receive part as working asynchronous if it helps. - DS:rcount:COUNTER:25:0: - DS:rmerged:COUNTER:25:0:U - DS:rbytes:COUNTER:25:0:U - DS:rtime:COUNTER:25:0:U - DS:wcount:COUNTER:25:0:U - DS:wmerged:COUNTER:25:0:U - DS:wbytes:COUNTER:25:0:U - DS:wtime:COUNTER:25:0:U - -=item Network traffic (FnameE>.rrd>) - - DS:incoming:COUNTER:25:0:U - DS:outgoing:COUNTER:25:0:U +In addition to the above, there are "logging plugins". Right now those are the +C and the C. With these plugins collectd can +provide information about issues and significant situations to the user. +Several loglevels let you suppress uninteresting messages. -=item Users (F) +Starting with version C<4.3.0> collectd has support for B. This is +done by checking thresholds defined by the user. If a value is out of range, a +notification will be dispatched to "notification plugins". See +L for more detailed information about threshold checking. - DS:users:GAUGE:25:0:65535 +Please note that some plugins, that provide other means of communicating with +the daemon, have manpages of their own to describe their functionality in more +detail. In particular those are L, L, +L, L, and L -=item VServer load (FxidE>/load.rrd>) - - DS:shortterm:GAUGE:25:0:100 - DS:midterm:GAUGE:25:0:100 - DS:longterm:GAUGE:25:0:100 - -=item VServer threads (FxidE>/threads.rrd>) - - DS:total:GAUGE:25:0:65535 - DS:running:GAUGE:25:0:65535 - DS:uninterruptible:GAUGE:25:0:65535 - DS:onhold:GAUGE:25:0:65535 +=head1 SIGNALS -=item VServer network traffic (FxidE>/traffic-InameE>.rrd>) +B accepts the following signals: - DS:incoming:COUNTER:25:0:9223372036854775807 - DS:outgoing:COUNTER:25:0:9223372036854775807 - DS:failed:COUNTER:25:0:9223372036854775807 +=over 4 -=item VServer processes (FxidE>/vs_processes.rrd>) +=item B, B - DS:total:GAUGE:25:0:65535 +These signals cause B to shut down all plugins and terminate. -=item VServer memory usage (FxidE>/vs_memory.rrd>) +=item B - DS:vm:GAUGE:25:0:9223372036854775807 - DS:vml:GAUGE:25:0:9223372036854775807 - DS:rss:GAUGE:25:0:9223372036854775807 - DS:anon:GAUGE:25:0:9223372036854775807 +This signal causes B to signal all plugins to flush data from +internal caches. E.Eg. the C will write all pending data +to the RRD files. This is the same as using the C command of the +C. =back =head1 SEE ALSO -L, L, L, L, -L +L, +L, +L, +L, +L, +L, +L, +L =head1 AUTHOR