Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Restart multiple services

Hi all - I have an application monitor with several windows service components. If a specific service is down, I would like SAM to start the service (which is easy), then wait 60 seconds and restart the other services. The problem is getting the componentID for the other services to plug into the APMServiceControl.exe ${N=SwisEntity;M=ComponentAlert.ComponentID}.

I suppose I could create a component alert unique to each server running the application, and hard code the variables, but that isn't very scalable.

Any thoughts?

Kevin

Find more posts tagged with

Accepted answers

All comments

adam.beedell

There's a few ways you could solve this

1) Set the alert to reset after the this action is taken (or add an action to clear the alert), when it next triggers it'll go one down the list

2) Set a custom resetter action, pump the full list of broken services to that (this is a faff, you'd be doing a select ID where type like service, port that to SQL, FOR XML PATH to a list, then replace into a nicely deliniated list, or maybe do that in the resetter action). Have the resetter action perform the action as before but looped with waits

3) Set up a series of escalation actions, select top 1 bad service per, hope you dont have a longer list of failures than the steps (could always have step 10 be "email 'this is left sort it yourself' "

4) Alert at the component layer where resets are needed, then you get an alert per thing with a reset trigger per thing.

Something like that

jklundy

Thanks Adam - if I understand your options, I don't think it solves my use case. It's not mutliple DOWN services. It is one down, but I need to restart 2. Service 2 needs a reset after Service 1 is up.

I am alerting at the component layer.

Along the lines of - IF DB is down, start DB. Wait 2 minutes, restart web application service.

adam.beedell

Oh interesting. You got a lot of these?

1) 2 alert actions with a wait

2) 2 alerts, one looking for the first being down, then one looking for the 2nd one being down (either slower, or AND looking for evidence of the first happening. EG, add an action to the first filling in a custom property, for the 2nd look for the presence of that property)

3) Custom resetter

BaldFeegle

I'd configure the alert to restart the first service upon detection. Then add an escalation level with a wait time of 2 mins and an action to restart the 2nd service.

You can use a SWQL variable to get the component ID of the service you want to restart. We do this if memory usage by the Netflow service gets too high it indicates we have a memory leak so we want to restart it automatically. You'd obviously need your own SWQL query but this should work as a starting point.

\Program Files (x86)\SolarWinds\Orion\APMServiceControl.exe ${N=SWQL;M=SELECT c.ComponentID FROM Orion.APM.Component C WHERE c.Name = 'Service: SolarWinds NetFlow Service' AND c.Application.NodeID = ${N=SwisEntity;M=Application.Node.NodeID}} -c=RESTART