nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Windows Services

FormerMember

Can the Orion APM be configured to restart a windows service if it see's the service go down?

Find more posts tagged with

monitor_service

apm

application_restart

restart_service

apm_features

Accepted answers

All comments

Yann

Hi,

The following should help you:

Restarting Windows Services with an Alert Action

Thanks,

Yann

borgan

How does this program work in conjunction with the Windows service recovery actions? Does it compete with it? Do I need to set all my service recovery actions to "Take No Action"?

qle

If anything, I imagine it would complement the recovery actions. Since the recovery actions are usually executed immediately, you can have the trigger delayed for a couple of minutes. If the service is still down, the alert will trigger. Then, you could have the the alert action repeat its attempt to restart the service at specific intervals until it's back up.

GarethHassall

One potential problem here is that the account under which Orion is running may not have the correct rights on the remote server. I don't see anywhere in the advanced alerts console to set which account should be used to issue the command to the other server's failed service.

josh.clark

One potential problem here is that the account under which Orion is running may not have the correct rights on the remote server. I don't see anywhere in the advanced alerts console to set which account should be used to issue the command to the other server's failed service.

The APMServiceControl utility take the Component Monitor Id of a Windows Service Monitor on the command line. Since this utility uses WMI to restart the service, we use the service name and credentials defined in the Component Monitor you specified.

GarethHassall

Thank you. I understand how that works now. It's not explicit in any of the documentation & making this clear might makes things easier for people who want to use this functionality.

RogerWong

Thanks for calling that out, Gareth. I'm rewriting that section accordingly.

gbutler

Hi Roger:

Has this documentation been created? I could use the help in understanding this better.

Glenn.

RogerWong

Glenn, if you have some specific questions, please ask away. I updated the Restarting Windows Services with an Alert Action last year to clarify the credentials issue mentioned earlier in this thread, but nothing further.

The one thing I need to clarify in the next revision is this:

You can't just restart any Windows service you want. You can only restart services you are actively monitoring using Orion APM.

Lets say you have an HTTP monitor set up to monitor a web site and want to create an alert action that restarts the IIS w3svc service if the website is down. You can't do that if you're only monitoring the web site. You have to also add a Windows service monitor to monitor the w3svc service. Otherwise, the utility we use to do the service restarting won't know how to find the service to restart.