Skip to content

Commit be56bc1

Browse files
committed
doc/03-Configuration.md: Mention forced log events
The logging was slightly modified in #920, resulting in a few log messages being shown regardless of the user configured log level. Since this may not be the expected behavior, it is now mentioned in the docs.
1 parent 209efac commit be56bc1

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

doc/03-Configuration.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,11 @@ For environment variables, each option is prefixed with `ICINGADB_LOGGING_`.
9999
| interval | **Optional.** Interval for periodic logging defined as [duration string](#duration-string). Defaults to `"20s"`. |
100100
| options | **Optional.** Map of component name to logging level in order to set a different logging level for each component instead of the default one. See [logging components](#logging-components) for details. |
101101

102+
!!! info
103+
104+
There are a few log messages that are logged regardless of the configured log level.
105+
For example, the startup message is always shown.
106+
102107
### Logging Components
103108

104109
The independent components of Icinga DB produce log entries.

0 commit comments

Comments
 (0)