If the service is started then the serviceStatus measure will record a “1”. If the service is stopped it will return “0”. In case of an access or other problem the plugin will fail to execute with an error message indicating the problem.
Windows Service Status Monitor Plugin 1.0.0 (compatible with dynaTrace 3.5.2+)
Not Supported If you have any questions or suggestions for these plugins, please add a comment to this page, use our forum, or drop us an email at email@example.com!
2012-03-05 Initial Release
Download current release from GitHub Project Page
The name of the service to monitor.
Since the plugin is using the SC command, this means that the logon account configured for the dynaTrace collector needs to have appropriate access to the host(s) you want to monitor (typically Administrator access to the server). If the access isn’t there, the monitor will fail with a detailed error message. A good way to test this is to log into the collector with the account it is running as, open a command prompt and execute a SC command to the remote server you want to monitor.
Import the Plugin into the dynaTrace Server. For details how to do this please refer to the dynaTrace documentation.
I am having trouble with this plugin, i installed it, setup the monitor but i receive this error. It just says 'FAILED' so i can't figure out
how to correct this. Any help would be appreciated.
Schedule DetailsName: Kofax Capture ExportStatus: scheduledDescription: The Windows Service Status Plugin returns the status of the specified service.Type: Windows Service Status MonitorLast Run: -Last Run Result: failedNext Run: -Current Run: -Duration (last run): -Schedule: Every 5 MinutesExecution Target: dynaTrace Collector@vsavdynatraceapmPlugin Active: activeResult Status: failedResult: 1 host queried, 1 failed or unknown, 0 partially failed and 0 successful.Result: Detailed information of failed last task/monitor execution is no longer available. Please trigger a new run.
I've installed this plugin for a customer but can't see any measures on the measures tab. Did anyone see that before?
We are experiencing the same issue... No measures listed in either the Measures tab and the Create Measure dialog.
Did you resolve the matter? If so, what did you do to fix this?
On the measures tab, if you go to Create Measure do they show there?
Has anyone figured out a way to configure the logon account configured for the dynaTrace collector that is not Administrator access and still enables the plugin to execute successfully?
I resolved the "FAILED" issue by doing the following:
Can this plugin be modified to test on multiple services? So under Monitor->Settings section provide an option to add multiple service names?
We have installed this plugin and getting an error while running the Plugin .Below is the error detail.Please help us with this issue.
Name: ddcsspsapp4b-tStatus: finishedDescription: Type: Windows Service Status MonitorLast Run: 08:11:42 (MST)Last Run Result: failedNext Run: -Current Run: -Duration (last run): < 1sSchedule: -Execution Target: ddcsapmapp01 9998@ddcsapmapp01Plugin Active: activeResult Status: failedResult: Last polling execution failedReason for failure: Error during execution of plug in occurredError message: Plugin unauthorizedDetailed error message: Error occurred
Please have a look at your Collector as you should have a log file written by this monitor plugin with a more detailed error description. You can find these log files through the System Information Dashlet - expand the tree all the way to the collector and then to log files. The log file name should reflect the name of your monitor
Just to echo what Ken said - that solved this issue for me. You have to have the logon user of the collector service added as an account with privileges to run the SC command on the server you are trying to monitor. You will continue to get this error until this is done.
Thank you all for the reply.
Could you please also let us know the SC command which you tried .
We checked the Collector log under system information in dynatrace client and could not find any details regarding the plugin .Also after enabling the plugin log file we ran the Windows Service Status Monitor Plugin and checked the log file and the file is of size 0KB. Please help us on this issue asap.
Could you please provide an update on the above issue as its a high priority task for me .
Have you followed the recommendations from Ken? Make sure that the collector runs under a windows account that has the required privileges. I also pinged the author of this plugin. As this is a community plugin from one of our users there is no guaranteed response time for questions. I do believe though that your problem is most likely related to what Ken and Brian were posting
Here are the steps you need to take:
1) Find out the Logon Account for the Collector Service. In Windows, this is going to be found by right clicking the service --> properties --> Logon Account. In Linux, it is the account that is running the Collector process.
2) Once you identify the Logon Account for the Collector process, that account needs to be given administrator privileges on the server you are trying to monitor with this plugin.
Thank you all & Brian.
I will perform the steps provided above .
The Collector service is running on the Local Service user account. So we will not be able to give permissions to that on the server we need to monitor.
Is there any other solution for this issue.
Thanks in advance.
In this case, you need to change it to another Logon User other than Local Service. You need to create a new service account that can run that service (or in my case, I just use my personal network login).
In order to change it to a new account simply right click --> properties --> logon user. And then change the Logon User field with the account you have designated to run the service other than Local Service. Be sure to put the full domain name in. For example - "NA\MyUserName"
In case if i change logon to my name/pwd . Do we have any other issue with connecting the agent and collecting pure path data. We have to try it on the production so i don't want to mess with any other things.
This should not impact collecting PurePath data. The only concern you should have is if your organization has a password expiration policy and in the event you forget to change your password on the Collector service, you could run into issues there.
That being said, I had the same concerns as you because I had to mess with the production Collector service.... So what I actually ended up doing was spinning up a separate Collector instance on the same server specifically dedicated to being the Windows Service Checker. With this, I did not have to worry about impacting the Collector that is used to collect PurePath data.
Documentation on how to install extra Collector instances are here if you want to take that route:
The plugin is running indefinitely. What could be the reason?
The plugin will run as long as you have an active schedule for it. If you want to stop a plugin you have to edit the monitor definition in your system profile. There in the System Profile -> Monitor Dialog you can stop monitor plugins
Is there a github available for this?
Hi. I just updated this page with the link to the GitHub page. Seems that link was missing: https://github.com/Dynatrace/Dynatrace-Windows-Service-Status-Monitor-Plugin