diff options
author | Lennart Poettering <lennart@poettering.net> | 2017-11-02 21:53:45 +0300 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2017-11-16 12:40:17 +0100 |
commit | 8b8de13d549d352825b3f2a14c55b1f82dbf64a8 (patch) | |
tree | 19ee154dfc56deccbaf101c035e96c0fb02ea5ee /man/systemd.exec.xml | |
parent | d3070fbdf6077d7da9dbafa198fff8dea712d2ff (diff) | |
download | systemd-8b8de13d549d352825b3f2a14c55b1f82dbf64a8.tar.gz |
man: document LogFieldMax= and LogExtraFields=
Diffstat (limited to 'man/systemd.exec.xml')
-rw-r--r-- | man/systemd.exec.xml | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index 4a97b1d203..d043555860 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -744,6 +744,41 @@ </varlistentry> <varlistentry> + <term><varname>LogLevelMax=</varname></term> + <listitem><para>Configures filtering by log level of log messages generated by this unit. Takes a + <command>syslog</command> log level, one of <option>emerg</option> (lowest log level, only highest priority + messages), <option>alert</option>, <option>crit</option>, <option>err</option>, <option>warning</option>, + <option>notice</option>, <option>info</option>, <option>debug</option> (highest log level, also lowest priority + messages). See <citerefentry + project='man-pages'><refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum></citerefentry> for + details. By default no filtering is applied (i.e. the default maximum log level is <option>debug</option>). Use + this option to configure the logging system to drop log messages of a specific service above the specified + level. For example, set <varname>LogLevelMax=</varname><option>info</option> in order to turn off debug logging + of a particularly chatty unit. Note that the the configured level is applied to any log messages written by any + of the processes belonging to this unit, sent via any supported logging protocol. The filtering is applied + early in the logging pipeline, before any kind of further processing is done. Moreover, messages which pass + through this filter successfully might still be dropped by filters applied at a later stage in the logging + subsystem. For example, <varname>MaxLevelStore=</varname> configured in + <citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> might + prohibit messages of higher log levels to be stored on disk, even though the per-unit + <varname>LogLevelMax=</varname> permitted it to be processed.</para></listitem> + </varlistentry> + + <varlistentry> + <term><varname>LogExtraFields=</varname></term> + <listitem><para>Configures additional log metadata fields to include in all log records generated by processes + associated with this unit. This setting takes one or more journal field assignments in the format + <literal>FIELD=VALUE</literal> separated by whitespace. See + <citerefentry><refentrytitle>systemd.journal-fields</refentrytitle><manvolnum>7</manvolnum></citerefentry> for + details on the journal field concept. Even though the underlying journal implementation permits binary field + values, this setting accepts only valid UTF-8 values. To include space characters in a journal field value, + enclose the assignment in double quotes ("). The usual specifiers are expanded in all assignments (see + below). Note that this setting is not only useful for attaching additional metadata to log records of a unit, + but given that all fields and values are indexed may also be used to implement cross-unit log record + matching. Assign an empty string to reset the list.</para></listitem> + </varlistentry> + + <varlistentry> <term><varname>TimerSlackNSec=</varname></term> <listitem><para>Sets the timer slack in nanoseconds for the executed processes. The timer slack controls the accuracy of |