Dear list,
while working with Icinga2, I noticed several characteristics regarding
the Icinga2 API and the config sync via API.
A short introduction to a setup:
2 masters, sharing the zone "master"
3 satellite zones with 2 or 1 satellite with parent zone "master"
New configuration is deployed
single services in case your data source
> provides such detailed information.
>
> As soon as your sync has a host and an object_name property for your
> services it would internally switch to using those as a combined key and
> succeed. The setup I'm currently working with
Hello,
i want to sync services via Director.
1. scenario: assign-filter
The importsource delivers the "import template name" and the "assign-filter"
2. scenario: hostname
The importsource delivers the "import template name" and the "hostname"
Neither 1 nor 2 i'm able to create
1. scenario
==
Thanks.
On 07.12.2016 09:31, Markus Frosch wrote:
On 06.12.2016 16:31, tilo@googlemail.com wrote:
in director/syncrule/addproperty its possible to choose as "Destination Field" "All
custom variables (vars.)"
I'm missing some information about the format of the
Hi,
in director/syncrule/addproperty its possible to choose as "Destination
Field" "All custom variables (vars.)"
I'm missing some information about the format of the Source Column.
Json? some kind of yaml?
Thanks
___
icinga-users mailing list
icing
dzone declared on the configmaster will be
replicated too.
The definition of the Ccildzone itself on the configmaster will not be
synced.
Best regards
On 15.11.2016 17:56, tilo@googlemail.com wrote:
Hi Stephan,
On 14.11.2016 21:14, Stephan Tesch wrote:
Am 14.11.2016 um 19:55 schrieb
Hi Tobias,
thanks for the reviewing.
On 15.11.2016 08:53, Tobias von der Krone wrote:
Hi Tilo,
On 2016-11-14 19:55, tilo@googlemail.com wrote:
Hi Stephan,
On 14.11.2016 16:20, Stephan Tesch wrote:
Am 14.11.2016 um 14:33 schrieb tilo@googlemail.com:
Hi Tilo,
Hallo,
we're
Hi Stephan,
On 14.11.2016 21:14, Stephan Tesch wrote:
Am 14.11.2016 um 19:55 schrieb tilo@googlemail.com:
on satA's:
=
/etc/icinga2.conf:
-
...
include zones.conf.d
include _recursive zones.conf.d
/etc/icinga2.zones.conf.d/satA
Hi Stephan,
On 14.11.2016 16:20, Stephan Tesch wrote:
Am 14.11.2016 um 14:33 schrieb tilo@googlemail.com:
Hi Tilo,
Hallo,
we're using an Master-Cluster with his own zone "master" and an
galera-sql-cluster for idodb.
The satellites (also HA-Cluster without idodb) are
Hallo,
we're using an Master-Cluster with his own zone "master" and an
galera-sql-cluster for idodb.
The satellites (also HA-Cluster without idodb) are located in own zones
"sat-cluster-location1", "sat-cluster-location" and so on.
All zone-configuration is done on the master.
The sync to t
t 16:30:54, tilo@googlemail.com wrote:
Hello,
its possible to build "High availability clusters" starting at 2 nodes.
Yes:
https://www.icinga.org/products/icinga-2/distributed-monitoring/
See also
http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/distributed-
monit
Hello,
its possible to build "High availability clusters" starting at 2 nodes.
Is there any split-brain detection?
Thanks in advance
Tilo Mey
___
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-
12 matches
Mail list logo