From be56bc12953d53f5b9ea53fec4b76ecb9a4d30eb Mon Sep 17 00:00:00 2001 From: Alvar Penning Date: Fri, 25 Apr 2025 13:28:14 +0200 Subject: [PATCH] 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. --- doc/03-Configuration.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/03-Configuration.md b/doc/03-Configuration.md index 2cd7900b..cccfd223 100644 --- a/doc/03-Configuration.md +++ b/doc/03-Configuration.md @@ -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.