Update documentation

doc/1-about.md

@@ -47,7 +47,7 @@ More details in the [Icinga FAQ](https://www.icinga.org/icinga/faq/).
 
 * [Register](https://exchange.icinga.org/authentication/register) an Icinga account.
 * Create a new issue at the [Icinga 2 Development Tracker](https://dev.icinga.org/projects/i2).
-* When reporting a bug, please include the details described in the [Troubleshooting](12-troubleshooting.md#troubleshooting-information-required) chapter (version, configs, logs, etc).
+* When reporting a bug, please include the details described in the [Troubleshooting](13-troubleshooting.md#troubleshooting-information-required) chapter (version, configs, logs, etc).
 
 ## <a id="whats-new"></a> What's new
 

doc/9-addons-plugins.md → doc/10-addons-plugins.md

@@ -8,19 +8,19 @@
 
 [PNP](http://www.pnp4nagios.org) must be configured using the
 [bulk mode with npcd and npcdmod](http://docs.pnp4nagios.org/pnp-0.6/modes#bulk_mode_with_npcd_and_npcdmod)
-hence Icinga 2's [PerfdataWriter](3-monitoring-basics.md#performance-data) acts as npcdmod. NPCD will collect
+hence Icinga 2's [PerfdataWriter](4-advanced-topics.md#performance-data) acts as npcdmod. NPCD will collect
 the rotated performance data files.
 
 #### <a id="addons-graphing-ingraph"></a> inGraph
 
 [inGraph](https://www.netways.org/projects/ingraph/wiki) requires the ingraph-collector addon
-to be configured to point at the perfdata files. Icinga 2's [PerfdataWriter](3-monitoring-basics.md#performance-data) will
+to be configured to point at the perfdata files. Icinga 2's [PerfdataWriter](4-advanced-topics.md#performance-data) will
 write to the performance data spool directory.
 
 #### <a id="addons-graphing-graphite"></a> Graphite
 
 There are Graphite addons available for collecting the performance data files as well. But
-natively you can use the [GraphiteWriter](3-monitoring-basics.md#graphite-carbon-cache-writer) feature.
+natively you can use the [GraphiteWriter](4-advanced-topics.md#graphite-carbon-cache-writer) feature.
 
 #### <a id="addons-reporting"></a> Icinga Reporting
 
@@ -39,7 +39,7 @@ based on your monitoring configuration and status data using [NagVis](http://www
 As well as the Icinga supported web interfaces (Classic UI 1.x, Web 1.x, Web 2) there are a
 number of community provided web interfaces too:
 
-* [Thruk](http://www.thruk.org) based on the [Livestatus](11-livestatus.md#setting-up-livestatus) feature
+* [Thruk](http://www.thruk.org) based on the [Livestatus](12-livestatus.md#setting-up-livestatus) feature
 
 
 ## <a id="plugins"></a> Plugins
@@ -54,7 +54,7 @@ list of popular community sites which host check plugins:
 * [Icinga Wiki](https://wiki.icinga.org)
 
 The recommended way of setting up these plugins is to copy them to a common directory
-and create a new global constant, e.g. `CustomPluginDir` in your [constants.conf](4-configuring-icinga-2.md#constants-conf)
+and create a new global constant, e.g. `CustomPluginDir` in your [constants.conf](5-configuring-icinga-2.md#constants-conf)
 configuration file:
 
     # cp check_snmp_int.pl /opt/monitoring/plugins
@@ -81,9 +81,9 @@ documentation and/or plugin provided README for installation instructions.
 Sometimes plugins contain hard-coded paths to other components. Instead of changing
 the plugin it might be easier to create logical links which is (more) update-safe.
 
-Each plugin requires a [CheckCommand](5-object-types.md#objecttype-checkcommand) object in your
-configuration which can be used in the [Service](5-object-types.md#objecttype-service) or
-[Host](5-object-types.md#objecttype-host) object definition.
+Each plugin requires a [CheckCommand](6-object-types.md#objecttype-checkcommand) object in your
+configuration which can be used in the [Service](6-object-types.md#objecttype-service) or
+[Host](6-object-types.md#objecttype-host) object definition.
 
 There are the following conventions to follow when adding a new command object definition:
 
@@ -93,7 +93,7 @@ in `[ ... ]` then for shell escaping.
 * Define a unique `prefix` for the command's specific command arguments. That way you can safely
 set them on host/service level and you'll always know which command they control.
 * Use command argument default values, e.g. for thresholds
-* Use [advanced conditions](5-object-types.md#objecttype-checkcommand) like `set_if` definitions.
+* Use [advanced conditions](6-object-types.md#objecttype-checkcommand) like `set_if` definitions.
 
 Example for a custom `my-snmp-int` check command:
 
@@ -123,7 +123,7 @@ Example for a custom `my-snmp-int` check command:
       vars.snmp_crit = "0,600"
     }
 
-Icinga 2 has built-in check command definitions for the [Manubulon Plugin Checks](6-icinga-template-library.md#snmp-manubulon-plugin-check-commands).
+Icinga 2 has built-in check command definitions for the [Manubulon Plugin Checks](7-icinga-template-library.md#snmp-manubulon-plugin-check-commands).
 
 For further information on your monitoring configuration read the
 [Monitoring Basics](3-monitoring-basics.md#monitoring-basics) chapter.
@@ -151,7 +151,7 @@ or similar.
 > **Tip**
 >
 > Get to know the new configuration format and the advanced [apply](3-monitoring-basics.md#using-apply) rules and
-> use [syntax highlighting](9-addons-plugins.md#configuration-syntax-highlighting) in vim/nano.
+> use [syntax highlighting](10-addons-plugins.md#configuration-syntax-highlighting) in vim/nano.
 
 If you're looking for puppet manifests, chef cookbooks, ansible recipes, etc - we're happy
 to integrate them upstream, so please get in touch at [https://support.icinga.org](https://support.icinga.org).

doc/10-alternative-frontends.md → doc/11-alternative-frontends.md

@@ -3,7 +3,7 @@
 ## <a id="setting-up-icinga-classic-ui"></a> Setting up Icinga Classic UI 1.x
 
 Icinga 2 can write `status.dat` and `objects.cache` files in the format that
-is supported by the Icinga 1.x Classic UI. [External commands](3-monitoring-basics.md#external-commands)
+is supported by the Icinga 1.x Classic UI. [External commands](4-advanced-topics.md#external-commands)
 (a.k.a. the "command pipe") are also supported. It also supports writing Icinga 1.x
 log files which are required for the reporting functionality in the Classic UI.
 
@@ -32,8 +32,8 @@ to satisfy this dependency:
 On all distributions other than Debian you may have to restart both your web
 server as well as Icinga 2 after installing the Classic UI package.
 
-Icinga Classic UI requires the [StatusDataWriter](3-monitoring-basics.md#status-data), [CompatLogger](3-monitoring-basics.md#compat-logging)
-and [ExternalCommandListener](3-monitoring-basics.md#external-commands) features.
+Icinga Classic UI requires the [StatusDataWriter](4-advanced-topics.md#status-data), [CompatLogger](4-advanced-topics.md#compat-logging)
+and [ExternalCommandListener](4-advanced-topics.md#external-commands) features.
 Enable these features and restart Icinga 2.
 
     # icinga2 feature enable statusdata compatlog command
@@ -57,7 +57,7 @@ please check the official [Icinga 1.x user interface documentation](http://docs.
 
 Icinga 2 can write to the same schema supplied by `Icinga IDOUtils 1.x` which
 is an explicit requirement to run `Icinga Web` next to the external command pipe.
-Therefore you need to setup the [DB IDO feature](2-getting-started.md#configuring-db-ido) remarked in the previous sections.
+Therefore you need to setup the [DB IDO feature](#configuring-db-ido) remarked in the previous sections.
 
 ### <a id="installing-icinga-web"></a> Installing Icinga Web 1.x
 
@@ -104,7 +104,7 @@ found in the [Icinga Web documentation](http://docs.icinga.org/latest/en/icinga-
 
     # icinga-web-clearcache
 
-Additionally you need to enable the `command` feature for sending [external commands](3-monitoring-basics.md#external-commands):
+Additionally you need to enable the `command` feature for sending [external commands](4-advanced-topics.md#external-commands):
 
     # icinga2 feature enable command
 
@@ -140,7 +140,7 @@ use one of the config packages:
  - `icinga-web-config-icinga2-ido-mysql`
  - `icinga-web-config-icinga2-ido-pgsql`
 
-These packages take care of setting up the [DB IDO](2-getting-started.md#configuring-db-ido) configuration,
+These packages take care of setting up the [DB IDO](#configuring-db-ido) configuration,
 enabling the external command pipe for Icinga Web and depend on
 the corresponding packages of Icinga 2.
 
@@ -157,7 +157,7 @@ When changing Icinga Web configuration files make sure to clear the config cache
 > **Note**
 >
 > If you are using an older version of Icinga Web, install it like this and adapt
-> the configuration manually as shown in [the RPM notes](10-alternative-frontends.md#icinga-web-rpm-notes):
+> the configuration manually as shown in [the RPM notes](11-alternative-frontends.md#icinga-web-rpm-notes):
 >
 > `apt-get install --no-install-recommends icinga-web`
 

doc/11-livestatus.md → doc/12-livestatus.md

@@ -8,15 +8,15 @@ status information. It can also be used to send commands.
 >
 > Only install the Livestatus feature if your web interface or addon requires
 > you to do so (for example, [Icinga Web 2](2-getting-started.md#setting-up-icingaweb2)).
-> [Icinga Classic UI](10-alternative-frontends.md#setting-up-icinga-classic-ui) and [Icinga Web](10-alternative-frontends.md#setting-up-icinga-web)
+> [Icinga Classic UI](11-alternative-frontends.md#setting-up-icinga-classic-ui) and [Icinga Web](11-alternative-frontends.md#setting-up-icinga-web)
 > do not use Livestatus as backend.
 
 The Livestatus component that is distributed as part of Icinga 2 is a
 re-implementation of the Livestatus protocol which is compatible with MK
 Livestatus.
 
 Details on the available tables and attributes with Icinga 2 can be found
-in the [Livestatus Schema](17-appendix.md#schema-livestatus) section.
+in the [Livestatus Schema](18-appendix.md#schema-livestatus) section.
 
 You can enable Livestatus using icinga2 feature enable:
 
@@ -59,7 +59,7 @@ Other to the Icinga 1.x Addon, Icinga 2 supports two socket types
 * Unix socket (default)
 * TCP socket
 
-Details on the configuration can be found in the [LivestatusListener](5-object-types.md#objecttype-livestatuslistener)
+Details on the configuration can be found in the [LivestatusListener](6-object-types.md#objecttype-livestatuslistener)
 object configuration.
 
 ### <a id="livestatus-get-queries"></a> Livestatus GET Queries
@@ -92,7 +92,7 @@ Example using the tcp socket listening on port `6558`:
 
 ### <a id="livestatus-command-queries"></a> Livestatus COMMAND Queries
 
-A list of available external commands and their parameters can be found [here](17-appendix.md#external-commands-list-detail)
+A list of available external commands and their parameters can be found [here](18-appendix.md#external-commands-list-detail)
 
     $ echo -e 'COMMAND <externalcommandstring>' | netcat 127.0.0.1 6558
 
@@ -185,10 +185,10 @@ Default separators.
   downtimes     | services  | status attributes
   timeperiods   | &nbsp;    | name and is inside flag
   endpoints     | &nbsp;    | config and status attributes
-  log           | services, hosts, contacts, commands | parses [compatlog](5-object-types.md#objecttype-compatlogger) and shows log attributes
-  statehist     | hosts, services | parses [compatlog](5-object-types.md#objecttype-compatlogger) and aggregates state change attributes
+  log           | services, hosts, contacts, commands | parses [compatlog](6-object-types.md#objecttype-compatlogger) and shows log attributes
+  statehist     | hosts, services | parses [compatlog](6-object-types.md#objecttype-compatlogger) and aggregates state change attributes
 
 The `commands` table is populated with `CheckCommand`, `EventCommand` and `NotificationCommand` objects.
 
-A detailed list on the available table attributes can be found in the [Livestatus Schema documentation](17-appendix.md#schema-livestatus).
+A detailed list on the available table attributes can be found in the [Livestatus Schema documentation](18-appendix.md#schema-livestatus).
 

doc/12-troubleshooting.md → doc/13-troubleshooting.md

@@ -8,7 +8,7 @@
 * Provide complete configuration snippets explaining your problem in detail
 * Provide complete logs targetting your problem
 * If the check command failed - what's the output of your manual plugin tests?
-* In case of [debugging](12-troubleshooting.md#debug) Icinga 2, the full back traces and outputs
+* In case of [debugging](13-troubleshooting.md#debug) Icinga 2, the full back traces and outputs
 
 ## <a id="troubleshooting-enable-debug-output"></a> Enable Debug Output
 
@@ -32,7 +32,7 @@ You can find the debug log file in `/var/log/icinga2/debug.log`.
 The `icinga2 object list` CLI command can be used to list all configuration objects and their
 attributes. The tool also shows where each of the attributes was modified.
 
-That way you can also identify which objects have been created from your [apply rules](15-language-reference.md#apply).
+That way you can also identify which objects have been created from your [apply rules](16-language-reference.md#apply).
 
     # icinga2 object list
 
@@ -91,13 +91,13 @@ You can also filter by name and type:
 
 ## <a id="check-command-definitions"></a> Where are the check command definitions?
 
-Icinga 2 features a number of built-in [check command definitions](6-icinga-template-library.md#plugin-check-commands) which are
+Icinga 2 features a number of built-in [check command definitions](7-icinga-template-library.md#plugin-check-commands) which are
 included using
 
     include <itl>
     include <plugins>
 
-in the [icinga2.conf](4-configuring-icinga-2.md#icinga2-conf) configuration file. These files are not considered configuration files and will be overridden
+in the [icinga2.conf](5-configuring-icinga-2.md#icinga2-conf) configuration file. These files are not considered configuration files and will be overridden
 on upgrade, so please send modifications as proposed patches upstream. The default include path is set to
 `LocalStateDir + "/share/icinga2/includes"`.
 
@@ -109,7 +109,7 @@ or similar.
 * Check the debug log 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](7-cli-commands.md#features) feature is enabled.
+* Make sure the [checker](8-cli-commands.md#features) feature is enabled.
 
 Examples:
 
@@ -131,7 +131,7 @@ Verify the following configuration
 * Do the notification attributes `states`, `types`, `period` match the notification conditions?
 * Do the user attributes `states`, `types`, `period` match the notification conditions?
 * Are there any notification `begin` and `end` times configured?
-* Make sure the [notification](7-cli-commands.md#features) feature is enabled.
+* Make sure the [notification](8-cli-commands.md#features) feature is enabled.
 * Does the referenced NotificationCommand work when executed as Icinga user on the shell?
 
 If notifications are to be sent via mail make sure that the mail program specified exists.
@@ -146,25 +146,25 @@ Examples:
 ## <a id="feature-not-working"></a> Feature is not working
 
 * Make sure that the feature configuration is enabled by symlinking from `features-available/`
-to `features-enabled` and that the latter is included in [icinga2.conf](4-configuring-icinga-2.md#icinga2-conf).
+to `features-enabled` and that the latter is included in [icinga2.conf](5-configuring-icinga-2.md#icinga2-conf).
 * Are the feature attributes set correctly according to the documentation?
 * Any errors on the logs?
 
 ## <a id="configuration-ignored"></a> Configuration is ignored
 
-* Make sure that the line(s) are not [commented out](15-language-reference.md#comments) (starting with `//` or `#`, or
+* Make sure that the line(s) are not [commented out](16-language-reference.md#comments) (starting with `//` or `#`, or
 encapsulated by `/* ... */`).
-* Is the configuration file included in [icinga2.conf](4-configuring-icinga-2.md#icinga2-conf)?
+* Is the configuration file included in [icinga2.conf](5-configuring-icinga-2.md#icinga2-conf)?
 
 ## <a id="configuration-attribute-inheritance"></a> Configuration attributes are inherited from
 
-Icinga 2 allows you to import templates using the [import](15-language-reference.md#template-imports) keyword. If these templates
+Icinga 2 allows you to import templates using the [import](16-language-reference.md#template-imports) keyword. If these templates
 contain additional attributes, your objects will automatically inherit them. You can override
 or modify these attributes in the current object.
 
 ## <a id="troubleshooting-cluster"></a> Cluster Troubleshooting
 
-You should configure the [cluster health checks](8-monitoring-remote-systems.md#cluster-health-check) if you haven't
+You should configure the [cluster health checks](9-monitoring-remote-systems.md#cluster-health-check) if you haven't
 done so already.
 
 > **Note**
@@ -218,7 +218,7 @@ If the cluster zones do not sync their configuration, make sure to check the fol
 * Within a config master zone, only one configuration master is allowed to have its config in `/etc/icinga2/zones.d`.
 ** The master syncs the configuration to `/var/lib/icinga2/api/zones/` during startup and only syncs valid configuration to the other nodes
 ** The other nodes receive the configuration into `/var/lib/icinga2/api/zones/`
-* The `icinga2.log` log file will indicate whether this ApiListener [accepts config](8-monitoring-remote-systems.md#zone-config-sync-permissions), or not
+* The `icinga2.log` log file will indicate whether this ApiListener [accepts config](9-monitoring-remote-systems.md#zone-config-sync-permissions), or not
 
 
 ## <a id="debug"></a> Debug Icinga 2