Re: [icinga-users] Run check only on active member of heartbeat cluster

[icinga]

Dne 21.2.2017 v 12:37 Werner Flamme napsal(a):
ici...@nomir.net [21.02.2017 12:28]:
Hi all,

I am trying to configure icinga2 to run some checks only on active
member of heartbeat cluster. I have created virtual host representing
cluster and two hosts representing cluster members. Services assigned to
cluster host monitoring the state of the whole cluster like virtual ip,
http response,... These checks are executed on monitoring server – no
problem. But some checks must be executed directly on active cluster
member with installed icinga agents.

I tried to determine service command_endpoint by function.

command_endpoint = {{ ..code to return active node.. }}

But this is not supported.

Any idea how to do it? Thanks

Mirek
When you have an virtual ip, which is always on the active host, you can
bin the commands to that ip address (or hostname, if available).

I have services running on alternate hosts, and if I want to check the
service, I check via its virtual ip, though I switch manually since I
want to avoid the complexity of heartbeat.

HTH, Werner

I tried to define new endpoint with cluster virtual IP. But this failed 
on certificate checks. I already have endpoints for cluster members.

[2017-02-21 13:51:53 +0000] information/JsonRpcConnection: Reconnecting 
to API endpoint 'cluster-hostname' via host 'IP' and port '5665'
[2017-02-21 13:51:53 +0000] warning/ApiListener: Unexpected certificate 
common name while connecting to endpoint 'cluster-hostname': got 
'cluster-member-hostname'

One possibility is to have two icinga agents on the same host with 
different certificates. But this is ugly solution.

My intention was changing command_endpoint dynamically. But all attempts 
to do it failed.

_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users