...
As you can see, all elements are in a unique realm. That's the sub-realm functionality used for reactionner/broker.
Variable Descriptions
| Property | Default | Description |
|---|---|---|
| realm_name | N/A | This variable is used to identify the *short name* of the realm. |
| realm_members | N/A | This directive is used to list realm sub-realms. |
| broker_complete_links | 0 | If 1, then the brokers will be allowed to talk to schedulers taht already have a broker defined (in its realm or upper). So enabling this option allow a scheduler to export its data to all the broker in its realm level or upper, whatever their number are. |
| default | 0 | This directive is used to define if the realm is the default one or not. Only one default realm is allowed. |
Example Definition
...
You first realm: World
| Code Block |
|---|
define realm{
realm_name World
realm_members Europe,America,Asia
default 0
} |
World
...
and its Sub-Realm ( configuration )
Here is the configuration for the shared architecture:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
define realm {
realm_name World
# Now you define SUB REALMS of World
realm_members Europe,US,Asia
# Element without explicit realm setting will be set in the World realm
default 1
}
# We define our SUB REALMS
# EUROPE
define realm{
realm_name Europe
# This one have it's own SUB REALM
realm_members Paris
}
# Paris: sub realm for Europe
define realm{
realm_name Paris
}
# USA
define realm{
realm_name USA
}
# Asia
define realm{
realm_name Asia
}
# For example the daemons for the Paris realm
define scheduler{
scheduler_name scheduler_Paris
realm Paris
}
# Example of a TOP level realm (WORLD) daemon that can reach daemons of the SUB realms
# so will reach Europe, Paris, USA and Asia
define reactionner{
reactionner_name reactionner-master
realm World
}
|
| Info |
|---|
| You must put the files in /etc/shinken/realms |
And the host link into a realm will be on the host configuration page:
...