From 4b18d6758759022090e185c4d7a021f7ff5d53fc Mon Sep 17 00:00:00 2001 From: Brendan Jurd Date: Fri, 14 Oct 2016 16:33:53 +1100 Subject: [PATCH] Fix bad heading level for {commands,groups}.conf The heading levels for commands.conf and groups.conf were incorrect. They should have been at level 4, underneath "4.2.3 The conf.d directory", but instead they were at level 3. fixes #12933 Signed-off-by: Jean Flach --- doc/4-configuring-icinga-2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/4-configuring-icinga-2.md b/doc/4-configuring-icinga-2.md index 9e455fa3f..5a54bd919 100644 --- a/doc/4-configuring-icinga-2.md +++ b/doc/4-configuring-icinga-2.md @@ -523,7 +523,7 @@ implicitely use the `icingaadmins` UserGroup defined in [users.conf](4-configuri More details on defining notifications and their additional attributes such as filters can be read in [this chapter](3-monitoring-basics.md#notifications). -### commands.conf +#### commands.conf This is the place where your own command configuration can be defined. By default only the notification commands used by the notification templates defined in [templates.conf](4-configuring-icinga-2.md#templates-conf). @@ -531,7 +531,7 @@ only the notification commands used by the notification templates defined in [te You can freely customize these notification commands, and adapt them for your needs. Read more on that topic [here](3-monitoring-basics.md#notification-commands). -### groups.conf +#### groups.conf The example host defined in [hosts.conf](hosts-conf) already has the custom attribute `os` set to `Linux` and is therefore automatically -- 2.40.0