summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2013-10-10 08:38:31 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2013-10-10 08:38:31 +0200
commit34afd49fca8bd2542ccde74218aaf677ed7156dd (patch)
treed0b3b40ce4aad7672357ad7ada1c72f5c69a9e33
parent754346dc9b651df8a79c247666bc330511ef6945 (diff)
downloadrsyslog-34afd49fca8bd2542ccde74218aaf677ed7156dd.tar.gz
rsyslog-34afd49fca8bd2542ccde74218aaf677ed7156dd.tar.bz2
rsyslog-34afd49fca8bd2542ccde74218aaf677ed7156dd.zip
doc: add minimum version requirements
-rw-r--r--doc/impstats.html14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/impstats.html b/doc/impstats.html
index 02e84e33..d47a85a1 100644
--- a/doc/impstats.html
+++ b/doc/impstats.html
@@ -27,22 +27,22 @@ settings, this impact may be noticeable (for high-load environments).
<p><b>Module Confguration Parameters</b>:</p>
<p>This module supports module parameters, only.
<ul>
- <li><strong>interval </strong>[seconds] (default 300 [5minutes])<br>
+ <li><b>interval </b>[seconds] (default 300 [5minutes])<br>
Sets the interval, in <b>seconds</b> at which messages are generated. Please note that the
actual interval may be a bit longer. We do not try to be precise and so the interval is
actually a sleep period which is entered after generating all messages. So the actual
interval is what is configured here plus the actual time required to generate messages.
In general, the difference should not really matter.
<br></li>
- <li><strong>facility </strong>[facility number]<br>
+ <li><b>facility </b>[facility number]<br>
The numerical syslog facility code to be used for generated messages. Default
is 5 (syslog). This is useful for filtering messages.
<br></li>
- <li><strong>severity </strong>[severity number]<br>
+ <li><b>severity </b>[severity number]<br>
The numerical syslog severity code to be used for generated messages. Default
is 6 (info).This is useful for filtering messages.
<br></li>
- <li><strong>resetCounters </strong>[<b>off</b>/on]<br>
+ <li><b>resetCounters </b>[<b>off</b>/on] - available since 7.5.3<br>
When set to "on", counters are automatically reset after they are emitted. In that
case, the contain only deltas to the last value emitted. When set
to "off", counters always accumulate their values.
@@ -56,19 +56,19 @@ settings, this impact may be noticeable (for high-load environments).
logs. This is the suggested method if deltas are not necessarily needed in
real-time.
<br></li>
- <li><strong>format </strong>[json/cee/<b>legacy</b>](rsyslog v6.3.8+ only)<br>
+ <li><b>format </b>[json/cee/<b>legacy</b>] - available since 6.3.8<br>
Specifies the format of emitted stats messages. The default of "legacy" is
compatible with pre v6-rsyslog. The other options provide support for
structured formats (note the "cee" is actually "project lumberack" logging).
<br></li>
- <li><strong>log.syslog </strong>[<b>on</b>/off] - available since 7.3.6<br>
+ <li><b>log.syslog </b>[<b>on</b>/off] - available since 7.3.6<br>
This is a boolean setting specifying if data should be sent
to the usual syslog stream. This is useful if custom formatting
or more elaborate processing is desired. However, output is placed
under the same restrictions as regular syslog data, especially in
regard to the queue position (stats data may sit for an extended
period of time in queues if they are full).<br></li>
- <li><strong>log.file </strong>[file name] - available since 7.3.6<br>
+ <li><b>log.file </b>[file name] - available since 7.3.6<br>
If specified, statistics data is written the specified file. For
robustness, this should be a local file. The file format cannot be
customized, it consists of a date header, followed by a colon,