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

Documentation: Remove duplicated information.

This commit is contained in:
Michael Friedrich 2013-10-18 00:27:04 +02:00
parent dd1ec43cd0
commit fb0a100e24
2 changed files with 1 additions and 41 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
doc/6-advanced-topics.md
View File

@ -1,45 +1,5 @@
# Advanced Topics
## Soft and Hard State Types
### Soft State Type
A `SOFT` state type is being entered when a service checks ends up in
a `NOT-OK` state and its check counter has not yet reached the
configured `max_check_attempts` attribute.
Additionally a `SOFT` state type happens when a service recovers
from a soft error changing from `NOT-OK` state to `OK` state.
`SOFT` states are logged as alerts and event commands are executed.
> **Note**
>
> Event commands can filter the `SOFT` state type by using the
> macro `$SERVICESTATETYPE$` and its value being `"SOFT"`.
### Hard State Type
A `HARD` state type happens when a service has been re-checked
as many times as the `max_check_attempts` attribute defines
being in a `NOT-OK` state during the entire re-check starting
with the first `NOT-OK` transition.
If a service state changes from one `NOT-OK` state into another
`NOT-OK` state (for example from `WARNING` to `CRITICAL`) this
is also considered a `HARD` state change.
Additionally a `HARD` state type happens when a service recovers
from a hard error changing from `NOT-OK` state to `OK` state.
`HARD` states are logged, event commands are executed and notifications
are triggered notifying all associated users.
> **Note**
>
> Event commands can filter the `HARD` state type by using the
> macro `$SERVICESTATETYPE$` and its value being `"HARD"`.
## Downtimes
Downtimes can be scheduled for planned server maintenance or

2
doc/8-differences-between-icinga-1x-and-2.md
View File

@ -3,7 +3,7 @@
## Configuration Format
Icinga 1.x supports two configuration formats: key-value-based settings in the
`icinga.cfg` cofiguration file and object-based in included files (`cfg_dir`,
`icinga.cfg` configuration file and object-based in included files (`cfg_dir`,
`cfg_file`). The path to the `icinga.cfg` configuration file must be passed to
the Icinga daemon at startup.