tyler.durden
/
icinga2
mirror of https://github.com/Icinga/icinga2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update documentation links

This commit is contained in:
Gunnar Beutner 2015-03-08 11:34:59 +01:00
parent e3b338848e
commit 3ed85aea31
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/10-icinga2-client.md
View File

@ -523,7 +523,7 @@ objects configured, only the check command definitions must be configured.
> **Note** > **Note**
> >
> Remote clients must explicitely accept commands in a similar > Remote clients must explicitely accept commands in a similar
> fashion as cluster nodes [accept configuration](#cluster-zone-config-sync). > fashion as cluster nodes [accept configuration](12-distributed-monitoring-ha.md#cluster-zone-config-sync).
> This is due to security reasons. > This is due to security reasons.
Edit the `api` feature configuration in `/etc/icinga2/features-enabled/api.conf` on your client Edit the `api` feature configuration in `/etc/icinga2/features-enabled/api.conf` on your client

6
doc/13-addons-plugins.md
View File

@ -29,8 +29,8 @@ Set `perfdata_spool_dir = /var/spool/icinga2/perfdata` and restart the `npcd` da
There's also an Icinga Web 2 module for direct PNP graph integration There's also an Icinga Web 2 module for direct PNP graph integration
available at https://exchange.icinga.org/icinga/PNP4Nagios available at https://exchange.icinga.org/icinga/PNP4Nagios
More information on [action_url as attribute](12-addons-plugins.md#addons-graphing-pnp-action-url) More information on [action_url as attribute](13-addons-plugins.md#addons-graphing-pnp-action-url)
and [graph template names](12-addons-plugins.md#addons-graphing-pnp-custom-templates). and [graph template names](13-addons-plugins.md#addons-graphing-pnp-custom-templates).
### <a id="addons-graphing-graphite"></a> Graphite ### <a id="addons-graphing-graphite"></a> Graphite
@ -223,7 +223,7 @@ This behavior changed in Icinga 2 compared to Icinga 1.x. Though there are certa
fix this: fix this:
* Create a symlink for example from the `templates.dist/check_ping.php` template to the actual check name in Icinga 2 (`templates/ping4.php`) * Create a symlink for example from the `templates.dist/check_ping.php` template to the actual check name in Icinga 2 (`templates/ping4.php`)
* Pass the check command name inside the [format template configuration](04-advanced-topics.md#writing-performance-data-files) * Pass the check command name inside the [format template configuration](4-advanced-topics.md#writing-performance-data-files)
The latter becomes difficult with agent based checks like NRPE or SSH where the first command argument acts as The latter becomes difficult with agent based checks like NRPE or SSH where the first command argument acts as
graph template identifier. There is the possibility to define the pnp template name as custom attribute graph template identifier. There is the possibility to define the pnp template name as custom attribute

2
doc/7-icinga-template-library.md
View File

@ -783,7 +783,7 @@ nscp_boot | **Optional.** Whether to use the --boot option. Defaults to tr
nscp_query | **Required.** The NSClient++ query. Try `nscp client -q x` for a list. nscp_query | **Required.** The NSClient++ query. Try `nscp client -q x` for a list.
nscp_arguments | **Optional.** An array of query arguments. nscp_arguments | **Optional.** An array of query arguments.
## <a id="nscp-check-local"></a> nscp-local-cpu ## <a id="nscp-check-local-cpu"></a> nscp-local-cpu
Check command object for the `check_cpu` NSClient++ plugin. Check command object for the `check_cpu` NSClient++ plugin.

2
doc/8-cli-commands.md
View File

@ -393,7 +393,7 @@ cleared after review.
## <a id="cli-command-variable"></a> CLI command: Troubleshoot ## <a id="cli-command-troubleshoot"></a> CLI command: Troubleshoot
Collects basic information like version, paths, log files and crash reports for troubleshooting purposes and prints them to a file or the console. See [troubleshooting](16-troubleshooting.md#troubleshooting-information-required). Collects basic information like version, paths, log files and crash reports for troubleshooting purposes and prints them to a file or the console. See [troubleshooting](16-troubleshooting.md#troubleshooting-information-required).