How do you restart a service if the node is not down

We have an issue where we have APM checking a webpage that sometimes goes into an unknown state not down and not up but we need to restart the world wide web service and that fixes the issue. My alert looks like the above screenshot.

How do I make the service restart without using third party tools like pstools and have Solarwinds do this or will you be including third party tools in the future?

Find more posts tagged with

Accepted answers

All comments

mcbridea

I'm checking on this one.

mcbridea

Does this do the trick? (From APM Admin Guide)

Restarting Windows Services with an Alert Action
You can use the alert trigger action "Execute program" to restart a Windows
service that is down. Orion APM restarts the service by running an included
program named APMServiceControl.exe . When given the Component ID
number of a Windows Service monitor, this program restarts the service using
the service name and credential defined in the monitor.
The Component ID number of a monitor is an internal designation. If the alert is
an APM Component-based alert, use the ${ComponentId} variable to pass the
Component ID to the program.
To manually determine the Component ID number, go to the Component Details
View in the Web Console. The number after AM: in the URL of the page is the
Component ID. For example:
localhost/.../MonitorDetails.aspx
Example Alert Manager Trigger Action to Restart a Windows Service
Execute program: APMServiceControl.exe ${ComponentId}

Using the Preconfigured Restart a Service Alert
The SolarWinds Orion Alert Manager includes a pre-configured alert called
Restart a Service that has a recovery action to restart a service if a Windows
service component monitor is down. You must enable this alert manually
because it is disabled by default.
To enable the Restart a Service alert:
1. Start Advanced Alert Manager in the Alerting, Reporting, and Mapping
program group.
2. Click Configure Alerts from the View menu.
3. Check Restart a Service.
4. Click Done.

profzoom1

I will have to check on that, I did not see this in the guide originally. I didn't know how to get that Component ID # and the restart a service alert included in Solarwinds had a 9 in it.

I will let you know if that fixes what I am trying to do but I am not sure why you just can't select restart and then add the service name. I know other programs are that easy to use kind of thought this would be a no brainer.

kasaff

Your best bet in this type of situation is to take the pre-configured alert, copy it, and modify from there. That way you'll have the default condition and won't have to jump through hoops.

In your screen shot, I'm not sure you have the trigger quite right. You have application equal to down, but then the component in various stages. If a component goes into, say, critical status, the application is not considered down. Down means unreachable.

So to start off, I would make my trigger condition look something like this:

Node name is equal to FSWFAQAApp01

Application Name is equal to Ernst Processing for ErnstQATesting

Component Name is Equal to WWW Publishing Service

Component Status is not equal to Up

We do not go off of service name because you can name a component anything - if you're monitoring the Print Spooler service you can name it Bob if you want to. That's why we go off of component type.