mirror of
https://github.com/Icinga/icinga2.git
synced 2025-07-16 10:14:28 +02:00
parent
f9c37524f1
commit
26f41502b4
@ -125,6 +125,7 @@ Attributes:
|
|||||||
service_dependencies|**Optional.** A list of services which this host depends on. Each array element must be a dictionary containing the keys "host" and "service". These dependencies are used to determine whether the host is unreachable.
|
service_dependencies|**Optional.** A list of services which this host depends on. Each array element must be a dictionary containing the keys "host" and "service". These dependencies are used to determine whether the host is unreachable.
|
||||||
groups |**Optional.** The service groups this service belongs to.
|
groups |**Optional.** The service groups this service belongs to.
|
||||||
notifications |**Optional.** Inline definition of notifications. Each dictionary item specifies a notification.<br /><br />The `templates` attribute can be used to specify an array of templates that should be inherited by the notification object.<br /><br />The new notification object's name is "hostname:service:notification" - where "notification" is the dictionary key in the notifications dictionary.
|
notifications |**Optional.** Inline definition of notifications. Each dictionary item specifies a notification.<br /><br />The `templates` attribute can be used to specify an array of templates that should be inherited by the notification object.<br /><br />The new notification object's name is "hostname:service:notification" - where "notification" is the dictionary key in the notifications dictionary.
|
||||||
|
authorities |**Optional.** A list of Endpoints on which this service check will be executed in a cluster scenario.
|
||||||
|
|
||||||
### <a id="objecttype-servicegroup"></a> ServiceGroup
|
### <a id="objecttype-servicegroup"></a> ServiceGroup
|
||||||
|
|
||||||
|
@ -232,6 +232,29 @@ You can find the state file in `/var/lib/icinga2/icinga2.state`. Before copying
|
|||||||
the state file you should make sure that all your cluster nodes are properly shut
|
the state file you should make sure that all your cluster nodes are properly shut
|
||||||
down.
|
down.
|
||||||
|
|
||||||
|
### Assign Services to Cluster Nodes
|
||||||
|
|
||||||
|
By default all services are distributed among the cluster nodes with the `Checker`
|
||||||
|
feature enabled.
|
||||||
|
If you require specific services to be only executed by one or more checker nodes
|
||||||
|
within the cluster, you must define `authorities` as additional service object
|
||||||
|
attribute. Required Endpoints must be defined as array.
|
||||||
|
|
||||||
|
object Host "dmz-host1" inherits "generic-host" {
|
||||||
|
services["dmz-oracledb"] = {
|
||||||
|
templates = [ "generic-service" ],
|
||||||
|
authorities = [ "icinga-node-1" ],
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
> **Tip**
|
||||||
|
>
|
||||||
|
> Most common usecase is building a classic Master-Slave-Setup. The master node
|
||||||
|
> does not have the `Checker` feature enabled, and the slave nodes are checking
|
||||||
|
> services based on their location, inheriting from a global service template
|
||||||
|
> defining the authorities.
|
||||||
|
|
||||||
|
|
||||||
## Dependencies
|
## Dependencies
|
||||||
|
|
||||||
Icinga 2 uses host and service dependencies as attribute directly on the host or
|
Icinga 2 uses host and service dependencies as attribute directly on the host or
|
||||||
|
Loading…
x
Reference in New Issue
Block a user