I’ve an “Apply Service” rule running a command script which checks multiple application services ( running or not running ) via ssh. This is setup like this to avoid multiple service checks for various hosts.
One cavate is that if one of the services is not running for whatever reason ( app is not deployed or app has some issue going on ), it alerts obviously. In scenario where services defined separately, I can put it in downtime until it gets fixed. I can’t do that in this case because I want to other services be monitored.
Is there a way that I can put the bad service in downtime and keep the remaining ones as monitored?
The usual plugin output is
App1 is running App2 is running App3 is running
“I’ve an Apply Service rule running a command script which checks multiple
application services (running or not running) via ssh.”
In a scenario where services are defined separately, I can put one in
downtime until it gets fixed. I can’t do that in this case because I want to
other services be monitored.
“Is there a way that I can put the bad service in downtime and keep the
remaining ones as monitored?”
Well, no, because as you say yourself, it is only one Service Check (as far as
Icinga is concerned).
Icinga does not care how complex a single Service Check is - it’s either in
OK, Warning or Alert state - it can’t be “4/5ths OK and 1/5th Alert”.