APMServiceControl

A couple questions:

1. Does the action start or restart a service? If it only starts, is there a way to trigger a restart or would that be executed differently (ie vbscript)

2. I know ${ComponentID} can be passed in to restart the service, but what is the actual value being used? Is the service named being pulled from the registry name value?

I wanted to use APM to check something (that wasn't the actual service) and have the APMServiceControl start a particular service. Since the service was being passed through the alerting variables, I wanted to know what manual value could be put in.

Thanks,

Byron

Find more posts tagged with

apmservicecontrol

trigger_restart

restart_service

Accepted answers

All comments

josh.clark

1. Yes, the utility can Start, Stop, and Restart a service. If you run it on the command line with no parameters it will output some help information

2. The utility needs to know what service to act upon, the credentials to use, the server name, etc. Rather than having to pass all this information on the command line, it simply takes the id of a Windows Service Component Monitor. As you stated, if this alert is an "APM: Component" based alert then you can just use the ${ComponentID} variable to uses the current component's id. You can also hard code the id to whatever makes sense for you. i.e.

APMServiceControl 37 -c=RESTART

To determine the component Id, just go to the Component Details View in the Web Console. The url will look something like this:

localhost/.../MonitorDetails.aspx

The number after "AM:" is the Component Id (11 in this case).

FormerMember

Great, that worked. I do have a followup question - which may need it's own thread.

So I have a Web Get setup on our web server. If the Web Get fails, I want Orion to restart the Web service on the remote server. Here's what I have setup in the alert:

Trigger Alert when All of the following apply

-Application Name is equal to WebGet .NET

-Application Status is equal to Down

Trigger Alert when all of the following apply

-Node Name contains IIS

-Component Name is equal to WS3SVC

I realize the bottom 'Condition Group' may be unneccesary with the way I have it setup. I have the ${ComponentID} passed into the APMServiceControl, however it is not yielding the correct Component. When I ran a test, it pulled a component from the correct server, but the wrong Component.

What I did next was delete the incorrect component being pulled and ran the test again. Same thing happened, only it pulled another incorrect Component.

Is this a bug or am I setting my alert variables incorrectly?

josh.clark

The Test Alert functionality does not work correctly with APM Alert objects. The Test Alert dialog doesn't give you a way to pick a specific Application or Component so it picks one at random from the node you selected.

FormerMember

Ok, makes sense. Now, I dunno if this is possible with Orion (maybe I will need to write a script instead), but just want to verify. With the following Trigger conditions:

*Trigger Alert when all of the following aply:
-Application Name is equal to WebGet .NET
-Application Status is equal to Down

For Trigger Actions, I have "C:\Program Files\Solarwinds\Orion\APM\APMServiceControl.exe" ${ComponentID}

Is there a way to set the ComponentID in the Trigger Conditions without being an actual requirement in the alert? I tried adding:

-ComponentName is equal to W3SVC

but this did not trigger the alert. With that line removed, the Trigger Actions will start, however, it is trying to restart the WebGet .NET application instead. I had an email sent after the first Trigger Action passing in ${ComponentID}.

I know I can put in the ComponentID manually with the number, however, we have this setup for about 50 servers. We also continuously add/remove servers into the farm.

wilbercollect

Thank you for the help. I spent days with Tech support and did not get this good of information. sometimes it is the little details that make a HUGE difference.