[collectd] [PATCH] types.db(5): Added a manpage documenting the format of the TypesDB file.

Sebastian Harl sh at tokkee.org
Sun Jan 20 22:17:23 CET 2008

Appropriate pointers have been added to other manpages where appropriate.

Signed-off-by: Sebastian Harl <sh at tokkee.org>
 .gitignore            |    1 +
 src/Makefile.am       |    5 ++-
 src/collectd-exec.pod |    3 +-
 src/collectd-perl.pod |    6 +++-
 src/collectd-snmp.pod |    2 +-
 src/collectd.conf.pod |    4 ++-
 src/collectd.pod      |    1 +
 src/types.db.pod      |   51 +++++++++++++++++++++++++++++++++++++++++++++++++
 8 files changed, 66 insertions(+), 7 deletions(-)
 create mode 100644 src/types.db.pod

diff --git a/.gitignore b/.gitignore
index 855e36b..5eb8974 100644
--- a/.gitignore
+++ b/.gitignore
@@ -46,6 +46,7 @@ src/*.o
diff --git a/src/Makefile.am b/src/Makefile.am
index 7f37fee..35d79c6 100644
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -633,7 +633,8 @@ endif
 dist_man_MANS = collectd.1 collectd-nagios.1 collectd.conf.5 \
 		collectd-email.5 collectd-exec.5 collectd-perl.5 \
-		collectd-snmp.5 collectd-unixsock.5 collectdmon.1
+		collectd-snmp.5 collectd-unixsock.5 collectdmon.1 \
+		types.db.5
 #collectd_1_SOURCES = collectd.pod
@@ -641,7 +642,7 @@ EXTRA_DIST = types.db
 EXTRA_DIST += collectd-email.pod collectd-exec.pod collectd-nagios.pod \
 	collectd-perl.pod collectd-snmp.pod collectd-unixsock.pod \
-	collectd.conf.pod collectd.pod collectdmon.pod
+	collectd.conf.pod collectd.pod collectdmon.pod types.db.pod
 	pod2man --release=$(VERSION) --center=$(PACKAGE) $< >.pod2man.tmp 2>/dev/null && mv -f .pod2man.tmp $@ || true
diff --git a/src/collectd-exec.pod b/src/collectd-exec.pod
index 4102136..7ef5428 100644
--- a/src/collectd-exec.pod
+++ b/src/collectd-exec.pod
@@ -46,7 +46,8 @@ omitted, too. I<plugin> and each I<instance>-part may be chosen freely as long
 as the tuple (plugin, plugin instance, type instance) uniquely identifies the
 plugin within collectd. I<type> identifies the type and number of values
 (i.E<nbsp>e. data-set) passed to collectd. A large list of predefined
-data-sets is available in the B<types.db> file.
+data-sets is available in the B<types.db> file. See L<types.db(5)> for a
+description of the format of this file.
 The I<OptionList> is an optional list of I<Options>, where each option if a
 key-value-pair. A list of currently understood options can be found below, all
diff --git a/src/collectd-perl.pod b/src/collectd-perl.pod
index b327ef5..eb0bd1d 100644
--- a/src/collectd-perl.pod
+++ b/src/collectd-perl.pod
@@ -193,9 +193,10 @@ argument which simply tells B<plugin_register> what is being registered.)
 The last argument, I<data>, is either a function name or an array-reference.
 If I<type> is B<TYPE_DATASET>, then the I<data> argument must be an
 array-reference which points to an array of hashes. Each hash describes one
-data-source. For the exact layout see B<Data-Set> above. Please note that
+data-set. For the exact layout see B<Data-Set> above. Please note that
 there is a large number of predefined data-sets available in the B<types.db>
-file which are automatically registered with collectd.
+file which are automatically registered with collectd - see L<types.db(5)> for
+a description of the format of this file.
 If the I<type> argument is any of the other types (B<TYPE_INIT>, B<TYPE_READ>,
 ...) then I<data> is expected to be a function name. If the name is not
@@ -439,6 +440,7 @@ instead.
diff --git a/src/collectd-snmp.pod b/src/collectd-snmp.pod
index ea49029..d0acc06 100644
--- a/src/collectd-snmp.pod
+++ b/src/collectd-snmp.pod
@@ -85,7 +85,7 @@ queried. The following options can be set:
 collectd's type that is to be used, e.E<nbsp>g. "if_octets" for interface
 traffic or "users" for a user count. The types are read from the B<TypesDB>
 (see L<collectd.conf(5)>), so you may want to check for which types are
+defined. See L<types.db(5)> for a description of the format of this file.
 =item B<Table> I<true|false>
diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod
index 7e416b4..4671ae1 100644
--- a/src/collectd.conf.pod
+++ b/src/collectd.conf.pod
@@ -74,7 +74,8 @@ Path to the plugins (shared objects) of collectd.
 =item B<TypesDB> I<File> [I<File> ...]
-Set one or more files that contain the data-set descriptions.
+Set one or more files that contain the data-set descriptions. See
+L<types.db(5)> for a description of the format of this file.
 =item B<Interval> I<Seconds>
@@ -1144,6 +1145,7 @@ L<collectd(1)>,
diff --git a/src/collectd.pod b/src/collectd.pod
index e09fd84..2a326bb 100644
--- a/src/collectd.pod
+++ b/src/collectd.pod
@@ -102,6 +102,7 @@ L<collectd-exec(5)>,
 =head1 AUTHOR
diff --git a/src/types.db.pod b/src/types.db.pod
new file mode 100644
index 0000000..f0a49f6
--- /dev/null
+++ b/src/types.db.pod
@@ -0,0 +1,51 @@
+=head1 NAME
+types.db - Data-set specifications for the system statistics collection daemon
+=head1 SYNOPSIS
+  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
+(":"): I<ds-name>:I<ds-type>:I<min>:I<max>. I<ds-type> may be either
+B<COUNTER> or B<GAUGE>. I<min> and I<max> define the range of valid values for
+data stored for this data-source. If B<U> is specified for either the min or
+max value, it will be set to unknown, meaning that no range checks will
+happen. See L<rrdcreate(1)> for more details.
+=head1 FILES
+The location of the types.db file is defined by the B<TypesDB> configuration
+option (see L<collectd.conf(5)>). If you want to specify custom data-sets, you
+should do so by using a custom file specified as an additional argument to the
+B<TypesDB> option.
+=head1 SEE ALSO
+=head1 AUTHOR
+B<collectd> has been written by Florian Forster
+This manpage has been written by Sebastian Harl

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://mailman.verplant.org/pipermail/collectd/attachments/20080120/72be8155/attachment-0001.pgp 

More information about the collectd mailing list