Hi,
Icinga 2 0.0.8 targets cluster & configuration finalization. Therefore
the current snapshot builds contain a simple cluster check which will
turn critical once one or more nodes go away.
It's an internal check method provided as check command by the ITL (a
package upgrade is required to latest snapshot builds).
http://docs.icinga.org/icinga2/snapshot/#cluster-health-check
My two test nodes are icinga2a (config master) and icinga2b (checker).
By killing off the remote node icinga2b, the documentation example check
will switch to critical. The 'authorities' attribute will make sure that
the service check is only executed on node icinga2a.
object Host "icinga2a" inherits "generic-host" {
services["cluster"] = {
templates = [ "generic-service" ],
check_interval = 1m,
check_command = "cluster",
authorities = [ "icinga2a" ]
},
}
You'll also recognize that the 'icinga' self stats check contains more
performance data values (*execution_time, states counters, etc) in order
to satisfy the ordinary icingastats output performance graphers.
http://docs.icinga.org/icinga2/snapshot/#itl-icinga
Have fun playing with Icinga 2 :)
--
DI (FH) Michael Friedrich
mail: [email protected]
twitter: https://twitter.com/dnsmichi
jabber: [email protected]
irc: irc.freenode.net/icinga dnsmichi
icinga open source monitoring
position: lead core developer
url: https://www.icinga.org
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
