From 593ddce21c27bc5627aae2be602884bae1c1898c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alexander=20Aleksandrovi=C4=8D=20Klimov?= Date: Wed, 23 Oct 2024 10:56:30 +0200 Subject: [PATCH] Update doc/15-troubleshooting.md Co-authored-by: alvar <8402811+oxzi@users.noreply.github.com> --- doc/15-troubleshooting.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/doc/15-troubleshooting.md b/doc/15-troubleshooting.md index d249d22fda..aac7696860 100644 --- a/doc/15-troubleshooting.md +++ b/doc/15-troubleshooting.md @@ -178,15 +178,14 @@ C:\ProgramData\icinga2\var\log\icinga2> Get-Content .\debug.log -tail 10 -wait ### Enable/Disable Debug Output on the fly -Every feature is just an Icinga 2 config object similar to Host and Service, e.g. -the `debuglog` feature is a [FileLogger](09-object-types.md#objecttype-filelogger). -Those can also be [managed via API](12-icinga2-api.md#icinga2-api-config-objects) -at runtime. This is a good alternative to `icinga2 feature enable debuglog`: +The `debuglog` feature can also be created and deleted at runtime without having to restart Icinga 2. +Technically, this is possible because this feature is a [FileLogger](09-object-types.md#objecttype-filelogger) +that can be managed through the [API](12-icinga2-api.md#icinga2-api-config-objects). -* Object creation/deletion via API happens immediately and requires no restart -* Hence, the debug log is enabled exactly as long as desired +This is a good alternative to `icinga2 feature enable debuglog` as object +creation/deletion via API happens immediately and requires no restart. -Both matter in setups large enough for the reload to take a while. +The above matters in setups large enough for the reload to take a while. Especially these produce a lot of debug log output until disabled again. !!! info