projects
/
collectd.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Merge branch 'collectd-5.4' into collectd-5.5
[collectd.git]
/
src
/
collectd-exec.pod
diff --git
a/src/collectd-exec.pod
b/src/collectd-exec.pod
index
5f2c687
..
0e4cd53
100644
(file)
--- a/
src/collectd-exec.pod
+++ b/
src/collectd-exec.pod
@@
-17,7
+17,7
@@
collectd-exec - Documentation of collectd's C<exec plugin>
=head1 DESCRIPTION
=head1 DESCRIPTION
-The C<exec plugin> forks of an executable either to receive values or to
+The C<exec plugin> forks of
f
an executable either to receive values or to
dispatch notifications to the outside world. The syntax of the configuration is
explained in L<collectd.conf(5)> but summarized in the above synopsis.
dispatch notifications to the outside world. The syntax of the configuration is
explained in L<collectd.conf(5)> but summarized in the above synopsis.
@@
-42,7
+42,7
@@
time and continuously write values to C<STDOUT>.
See L<EXEC DATA FORMAT> below for a description of the output format expected
from these programs.
See L<EXEC DATA FORMAT> below for a description of the output format expected
from these programs.
-B<Warning:> If the executable only writes one value and then exits
I
will be
+B<Warning:> If the executable only writes one value and then exits
it
will be
executed every I<Interval> seconds. If I<Interval> is short (the default is 10
seconds) this may result in serious system load.
executed every I<Interval> seconds. If I<Interval> is short (the default is 10
seconds) this may result in serious system load.
@@
-201,13
+201,13
@@
The data is passed to the executables over C<STDIN> in a format very similar to
HTTP: At first there is a "header" with one line per field. Every line consists
of a field name, ended by a colon, and the associated value until end-of-line.
The "header" is ended by two newlines immediately following another,
HTTP: At first there is a "header" with one line per field. Every line consists
of a field name, ended by a colon, and the associated value until end-of-line.
The "header" is ended by two newlines immediately following another,
-i.
E<nbsp>e. an empty line. The rest, basically the "body", is the message of
-
the
notification.
+i.
e. an empty line. The rest, basically the "body", is the message of the
+notification.
The following is an example notification passed to a program:
Severity: FAILURE
The following is an example notification passed to a program:
Severity: FAILURE
- Time: 1200928930
+ Time: 1200928930
.515
Host: myhost.mydomain.org
\n
This is a test notification to demonstrate the format
Host: myhost.mydomain.org
\n
This is a test notification to demonstrate the format
@@
-223,7
+223,9
@@
Severity of the notification. May either be B<FAILURE>, B<WARNING>, or B<OKAY>.
=item B<Time>
=item B<Time>
-The time in epoch, i.E<nbsp>e. as seconds since 1970-01-01 00:00:00 UTC.
+The time in epoch, i.e. as seconds since 1970-01-01 00:00:00 UTC. The value
+currently has millisecond precision (i.e. three decimal places), but scripts
+should accept arbitrary numbers of decimal places, including no decimal places.
=item B<Host>
=item B<Host>