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.
This commit is contained in:
Alvar Penning 2025-04-25 13:28:14 +02:00
parent 209efac134
commit be56bc1295
No known key found for this signature in database

View file

@ -99,6 +99,11 @@ For environment variables, each option is prefixed with `ICINGADB_LOGGING_`.
| interval | **Optional.** Interval for periodic logging defined as [duration string](#duration-string). Defaults to `"20s"`. |
| 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. |
!!! info
There are a few log messages that are logged regardless of the configured log level.
For example, the startup message is always shown.
### Logging Components
The independent components of Icinga DB produce log entries.