Skip to content

Commit

Permalink
Update doc/15-troubleshooting.md
Browse files Browse the repository at this point in the history
Co-authored-by: alvar <8402811+oxzi@users.noreply.github.com>
  • Loading branch information
Al2Klimov and oxzi committed Oct 23, 2024
1 parent 4fea1ef commit 593ddce
Showing 1 changed file with 6 additions and 7 deletions.
13 changes: 6 additions & 7 deletions doc/15-troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -178,15 +178,14 @@ C:\ProgramData\icinga2\var\log\icinga2> Get-Content .\debug.log -tail 10 -wait

### Enable/Disable Debug Output on the fly <a id="troubleshooting-enable-disable-debug-output-api"></a>

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
Expand Down

0 comments on commit 593ddce

Please sign in to comment.