Show Table of Contents
3.3.3. Logging
By default, log output is sent to
stderr if the broker is run on the command line, or to syslog (/var/log/messages/), if the broker is run as a service.
Table 3.1. Logging Options
Options for logging with syslog | |
|---|---|
-t [--trace] | Enables all logging |
--log-disable RULE | Disables logging for selected levels and components (opt-out). RULE is in the form LEVEL[+]:[:PATTERN]. Levels are one of: trace, debug, info, notice, warning, error, critical.. This allows uninteresting log messages to be dropped during debugging. This can be used multiple times. |
--log-enable RULE (notice+) | Enables logging for selected levels and components. RULE is in the form LEVEL[+]:[:PATTERN]. Levels are one of: trace, debug, info, notice, warning, error, critical.. For example: --log-enable warning+ logs all warning, error, and critical messages. --log-enable debug:framing logs debug messages from the framing namespace. This can be used multiple times. |
--log-time yes|no | Include time in log messages |
--log-level yes|no | Include severity level in log messages |
--log-source | Include source file:line in log messages |
--log-thread yes|no | Include thread ID in messages |
--log-function yes|no | Include function signature in log messages |
--log-hires-timestamp yes|no (0) | Use hi-resolution timestamps in log messages |
--log-category yes|no (1) | Include category in log messages |
--log-prefix STRING | Prefix to append to all log messages |
--log-to-stderr yes|no | Send logging output to stderr. Enabled by default when run from command line. |
--log-to-stdout yes|no | Send logging output to stdout. |
--log-to-file FILE | Send log output to the specified filename. FILE. |
--log-to-syslog yes|no | Send logging output to syslog. Enabled by default when run as a service. |
--syslog-name NAME | Specify the name to use in syslog messages. The default is qpidd. |
--syslog-facility LOG_XXX | Specify the facility to use in syslog messages. The default is LOG_DAEMON. |
See Also:
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.