Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

types.db(5) [debian man page]

TYPES.DB(5)							     collectd							       TYPES.DB(5)

NAME
types.db - Data-set specifications for the system statistics collection daemon collectd SYNOPSIS
bitrate value:GAUGE:0:4294967295 counter value:COUNTER:U:U if_octets rx:COUNTER:0:4294967295, tx:COUNTER:0:4294967295 DESCRIPTION
The types.db file contains one line for each data-set specification. Each line consists of two fields delimited by spaces and/or horizontal tabs. The first field defines the name of the data-set, while the second field defines a list of data-source specifications, delimited by spaces and, optionally, a comma (",") right after each list-entry. The format of the data-source specification has been inspired by RRDtool's data-source specification. Each data-source is defined by a quadruple made up of the data-source name, type, minimal and maximal values, delimited by colons (":"): ds-name:ds-type:min:max. ds-type may be either ABSOLUTE, COUNTER, DERIVE, or GAUGE. min and max define the range of valid values for data stored for this data-source. If U is specified for either the min or max value, it will be set to unknown, meaning that no range checks will happen. See rrdcreate(1) for more details. FILES
The location of the types.db file is defined by the TypesDB configuration option (see collectd.conf(5)). It defaults to collectd's shared data directory, i. e. prefix/share/collectd/. CUSTOM TYPES
If you want to specify custom types, you should do so by specifying a custom file in addition to the default one (see FILES) above. You can do that by having multiple TypesDB statements in your configuration file or by specifying more than one file in one line. For example: TypesDB "/opt/collectd/share/collectd/types.db" TypesDB "/opt/collectd/etc/types.db.custom" Note: Make sure to make this file available on all systems if you're sending values over the network. SEE ALSO
collectd(1), collectd.conf(5), rrdcreate(1) AUTHOR
collectd has been written by Florian Forster <octo at verplant.org>. This manpage has been written by Sebastian Harl <sh at tokkee.org>. 5.1.0 2012-04-02 TYPES.DB(5)

Check Out this Related Man Page

COLLECTD-EMAIL(5)						     collectd							 COLLECTD-EMAIL(5)

NAME
collectd-email - Documentation of collectd's "email plugin" SYNOPSIS
# See collectd.conf(5) LoadPlugin email # ... <Plugin email> SocketGroup "collectd" SocketPerms "0770" MaxConns 5 </Plugin> DESCRIPTION
The "email plugin" opens an UNIX-socket over which one can submit email statistics, such as the number of "ham", "spam", "virus", etc. mails received/handled, spam scores and matched spam checks. This plugin is intended to be used with the Mail::SpamAssassin::Plugin::Collectd SpamAssassin-plugin which is included in contrib/, but is of course not limited to that use. OPERATION
This plugin collects data indirectly by providing a UNIX-socket that external programs can connect to. A simple line based protocol is used to communicate with the plugin: o E-Mail type (e.g. "ham", "spam", "virus", ...) and size (bytes): e:<type>:<size> If "size" is less than or equal to zero, "size" is ignored. o Spam score: s:<value> o Successful spam checks (e.g. "BAYES_99", "SUBJECT_DRUG_GAP_C", ...): c:<type1>[,<type2>,...] Each line is limited to 256 characters (including the newline character). Longer lines will be ignored. SEE ALSO
collectd(1), collectd.conf(5) AUTHOR
The "email plugin" has been written by Sebastian Harl <sh at tokkee.org>. The SpamAssassin-plugin has been written by Alexander Wirt <formorer at formorer.de>. This manpage has been written by Florian Forster <octo at verplant.org>. 5.1.0 2012-04-02 COLLECTD-EMAIL(5)
Man Page