Is it possible to configure ntservices to only send an alarm when the automatical restart of a service failed?
When the restart was successful, an informational alarm should be sent, but not the normal down alarm.
You should be able to just have to disabled or modify the service down monitor but there is a alarm for service restart or restart failed.
A service restart is not detected.
When the service is down and the probe restarts it, the down alarm is sent, and cleared at the next cycle.
To my undestanding there should only be an informational alarm in this case.
Does it work as designed?
There should be a message in the config for restarting the service, make sure your service is set to restart and not just report as well.
I opened a Nimsoft case for this.
We found out that the behaviour if completely different when the action is set to "auto" (which I did at the beginning) than "force state".
"Force state" is almost what I need.
What I'm wondering is how do you configure the ntservices probe so that it throws an alarm when it tries to restart a service that it was monitoring and was detected as stopped? We want to be notified when it does a restart of a service.
ATM, we are monitoring all services on a box that are set to Automatic and if any are detected Stopped, we want it to try restarting the service one time. If it can't start the service then throw the "Service not running alert." an alert.
But we were wondering if the probe goes into a constant restart loop, service stops, probe restarts, service stops, probe restarts it, is this condition captured? If so how? What needs to be set in the probe to capture stop/restart/stop/restart loops?
Retrieving data ...