tyler.durden/icinga2
1
0
Fork 0
mirror of https://github.com/Icinga/icinga2.git synced 2025-04-08 17:05:25 +02:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Add object type IcingaDB

Browse Source
This commit is contained in:
Michael Friedrich 2019-11-02 17:34:00 +01:00
parent 631a4ee9fa
commit c3f6fa2e41
3 changed files with 27 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/09-object-types.md
View File

@ -1379,6 +1379,30 @@ Configuration Attributes:
vars | Dictionary | **Optional.** A dictionary containing custom variables that are available globally.
environment | String | **Optional.** Specify the Icinga environment. This overrides the `Environment` constant specified in the configuration or on the CLI with `--define`. Defaults to empty.
### IcingaDB <a id="objecttype-icingadb"></a>
The IcingaDB object implements the [icingadb feauture](14-features.md#core-backends-icingadb).
Example:
```
object IcingaDB "icingadb" {
//host = "127.0.0.1"
//port = 6379
//password = "xxx"
}
```
Configuration Attributes:
Name | Type | Description
--------------------------|-----------------------|----------------------------------
host | String | **Optional.** Redis host for IcingaDB. Defaults to `127.0.0.1`.
port | Number | **Optional.** Redis port for IcingaDB. Defaults to `6379`.
path | String | **Optional.** Redix unix socket path. Can be used instead of `host` and `port` attributes.
password | String | **Optional.** Redis auth password for IcingaDB.
### IdoMySqlConnection <a id="objecttype-idomysqlconnection"></a>
IDO database adapter for MySQL.

4
doc/15-troubleshooting.md
View File

@ -1626,9 +1626,9 @@ it is valid to just sync their zones via the config sync.
The following restores the Zone/Endpoint objects as config objects outside of `zones.d`
in your master/satellite's zones.conf with rendering them as external objects in the Director.
[Example](06-distributed-monitoring.md#three-levels-with-masters-satellites-and-agents)
[Example](06-distributed-monitoring.md#distributed-monitoring-scenarios-master-satellite-agents)
for a 3 level setup with the masters and satellites knowing about the zone hierarchy
outside defined in [zones.conf](#zones-conf):
outside defined in [zones.conf](04-configuration.md#zones-conf):
```
object Endpoint "icinga-master1.localdomain" {

2
doc/16-upgrading-icinga-2.md
View File

@ -188,7 +188,7 @@ being set but no `zone` defined.
The most convenient way with e.g. managing the objects in `conf.d`
is to move them into the `master` zone. Please continue in the
[troubleshooting docs](#troubleshooting-cluster-command-endpoint-errors-agent-hosts-command-endpoint-zone)
[troubleshooting docs](15-troubleshooting.md#troubleshooting-cluster-command-endpoint-errors-agent-hosts-command-endpoint-zone)
for further instructions.
#### Config Sync <a id="upgrading-to-2-11-cluster-config-sync"></a>