Docs: Add a note for Windows debuglog to the troubleshooting chapter

diff --git a/doc/15-troubleshooting.md b/doc/15-troubleshooting.md
index dc6038c439c07f0b0fcfccf797c0136f68589218..c3869a8514180c582e35861f4ef915280a8a098e 100644 (file)
--- a/doc/15-troubleshooting.md
+++ b/doc/15-troubleshooting.md
@@ -109,6 +109,8 @@ checks later on.
 
 ## <a id="troubleshooting-enable-debug-output"></a> Enable Debug Output
 
+### <a id="troubleshooting-enable-debug-output-linux"></a> Enable Debug Output on Linux/Unix
+
 Enable the `debuglog` feature:
 
     # icinga2 feature enable debuglog
@@ -124,6 +126,18 @@ log severity as an additional parameter argument to `-x`.
 The [log severity](9-object-types.md#objecttype-filelogger) can be one of `critical`, `warning`, `information`, `notice`
 and `debug`.
 
+### <a id="troubleshooting-enable-debug-output-windows"></a> Enable Debug Output on Windows
+
+Open a command prompt with administrative privileges and enable the debug log feature.
+
+    C:> icinga2.exe enable feature debuglog
+
+Ensure that the Icinga 2 service already writes the main log into `C:\ProgramData\icinga2\var\log\icinga2`.
+Restart the Icinga 2 service and open the newly created `debug.log` file.
+
+    C:> net stop icinga2
+    C:> net start icinga2
+
 ## <a id="list-configuration-objects"></a> List Configuration Objects
 
 The `icinga2 object list` CLI command can be used to list all configuration objects and their