bitrate value:GAUGE:0:4294967295 counter value:COUNTER:U:U if_octets rx:COUNTER:0:4294967295, tx:COUNTER:0:4294967295
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.
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/.
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.
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.
collectd(1), collectd.conf(5), rrdcreate(1)
collectd has been written by Florian Forster <octo at collectd.org>.
This manpage has been written by Sebastian Harl <sh at tokkee.org>.
collectd(1), collectd.conf(5), collectdctl(1), collectd-exec(5), collectd-java(5), collectd-perl(5), collectd-python(5), collectd-snmp(5).