Add a note on Windows NSClient++ CPU checks to the docs

refs #6315
This commit is contained in:
Michael Friedrich 2018-05-18 10:43:20 +02:00
parent a5a2194fa2
commit a926defb79
2 changed files with 12 additions and 0 deletions

View File

@ -2296,6 +2296,12 @@ Open Icinga Web 2 and check your newly added Windows NSClient++ check :)
![Icinga 2 Distributed Monitoring Windows Client with NSClient++ nscp-local](images/distributed-monitoring/icinga2_distributed_windows_nscp_counter_icingaweb2.png)
> **Tip**
>
> In order to measure CPU load, you'll need a running NSClient++ service.
> Therefore it is advised to use a local [nscp-api](06-distributed-monitoring.md#distributed-monitoring-windows-nscp-check-api)
> check against its REST API.
## Advanced Hints <a id="distributed-monitoring-advanced-hints"></a>
You can find additional hints in this section if you prefer to go your own route

View File

@ -1786,6 +1786,12 @@ nscp_query | **Required.** The NSClient++ query. Try `nscp client -q x` for
nscp_arguments | **Optional.** An array of query arguments.
nscp_showall | **Optional.** Shows more details in plugin output, default to false.
> **Tip**
>
> In order to measure CPU load, you'll need a running NSClient++ service.
> Therefore it is advised to use a local [nscp-api](06-distributed-monitoring.md#distributed-monitoring-windows-nscp-check-api)
> check against its REST API.
### nscp-local-cpu <a id="nscp-check-local-cpu"></a>
Check command object for the `check_cpu` NSClient++ plugin.