From: Michael Friedrich <michael.friedrich@netways.de>
Date: Wed, 13 Jan 2016 15:48:43 +0000 (+0100)
Subject: Troubleshooting: Explain how to fetch the executed command
X-Git-Tag: v2.5.0~624
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c49fed204a86c2fe59bd9728696ee8a43f38025b;p=icinga2

Troubleshooting: Explain how to fetch the executed command

fixes #10964
---

diff --git a/doc/16-troubleshooting.md b/doc/16-troubleshooting.md
index 3ce32b434..faf6a85eb 100644
--- a/doc/16-troubleshooting.md
+++ b/doc/16-troubleshooting.md
@@ -113,9 +113,19 @@ on upgrade, so please send modifications as proposed patches upstream. The defau
 You should add your own command definitions to a new file in `conf.d/` called `commands.conf`
 or similar.
 
-## <a id="checks-not-executed"></a> Checks are not executed
+## <a id="troubleshooting-checks"></a> Checks
 
-* Check the debug log to see if the check command gets executed
+### <a id="checks-executed-command"></a> Executed Command for Checks
+
+* Use the Icinga 2 API to [query](9-icinga2-api.md#icinga2-api-config-objects-query) host/service objects
+for their check result containing the executed shell command.
+* Use the Icinga 2 [console cli command](8-cli-commands.md#cli-command-console)
+to fetch the checkable object, its check result and the executed shell command.
+* Alternatively enable the [debug log](16-troubleshooting.md#troubleshooting-enable-debug-output) and look for the executed command.
+
+### <a id="checks-not-executed"></a> Checks are not executed
+
+* Check the [debug log](16-troubleshooting.md#troubleshooting-enable-debug-output) to see if the check command gets executed
 * Verify that failed depedencies do not prevent command execution
 * Make sure that the plugin is executable by the Icinga 2 user (run a manual test)
 * Make sure the [checker](8-cli-commands.md#enable-features) feature is enabled.