Icon

Comments have been closed on this page. Please use AppMon & UEM Plugins forum for questions about this plugin.

Overview

The plugin is querying the specified service on the given host(s) using the Windows SC command which communicates with the NT Service Controller and Services.


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.

Plugin Details

Plug-In Versions

Windows Service Status Monitor Plugin 1.0.0 (compatible with dynaTrace 3.5.2+)

Author

Derek Abing

License

dynaTrace BSD

Support

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 community@dynatrace.com!

Known Problems

 

Release History

2012-03-05 Initial Release

Download current release from GitHub Project Page

Provided Measures

  • serviceStatus: If the service is running, the measure will yield 1, otherwise 0.

Configuration

Name

Value

Service

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.

Installation

Import the Plugin into the dynaTrace Server. For details how to do this please refer to the dynaTrace documentation.

  1. Anonymous (login to see details)

    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 Details
    Name: Kofax Capture Export
    Status: scheduled
    Description: The Windows Service Status Plugin returns the status of the specified service.
    Type: Windows Service Status Monitor
    Last Run: -
    Last Run Result: failed
    Next Run: -
    Current Run: -
    Duration (last run): -
    Schedule: Every 5 Minutes
    Execution Target: dynaTrace Collector@vsavdynatraceapm
    Plugin Active: active
    Result Status: failed
    Result: 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.

  2. Anonymous (login to see details)

    I've installed this plugin for a customer but can't see any measures on the measures tab. Did anyone see that before?

    1. Anonymous (login to see details)

      Ran,

      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?

      Francois

  3. Anonymous (login to see details)

    On the measures tab, if you go to Create Measure do they show there?

  4. Anonymous (login to see details)

    Hi all,

    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?

    Thanks,

    Luis

  5. Anonymous (login to see details)

    I resolved the "FAILED" issue by doing the following:

    1. Run the dynatrace collector service (in the context of which the plugin will run) as a service account on the domain which the collector machine is running on. Service accounts are non-interactive and their passwords never expire.
    2. On the server where the collector is installed, go the installed folder location called "collector" and ensure that this service account has full access to it and all sub-folders.
    3. On the destination server, i.e. from where you want to fetch the status of a service, add this account to the list of admins.
    4. If the above listed steps dont resolve then try these additionally:
      1. May also be worth checking firewalls (either at the server(s) or a loadbalancer in between.
      2. Also check that you can reach the server(s) which could be in a DMZ.
  6. Anonymous (login to see details)

    Can this plugin be modified to test on multiple services? So under Monitor->Settings section provide an option to add multiple service names?

  7. Anonymous (login to see details)

    Hi Team,

    We have installed this  plugin and getting an error while running the Plugin .Below is the error detail.Please help us with this issue.

    Schedule Details

    Name: ddcsspsapp4b-t
    Status: finished
    Description:
    Type: Windows Service Status Monitor
    Last Run: 08:11:42 (MST)
    Last Run Result: failed
    Next Run: -
    Current Run: -
    Duration (last run): < 1s
    Schedule: -
    Execution Target: ddcsapmapp01 9998@ddcsapmapp01
    Plugin Active: active
    Result Status: failed
    Result: Last polling execution failed
    Reason for failure: Error during execution of plug in occurred
    Error message: Plugin unauthorized
    Detailed error message: Error occurred

     

    Regards,

    Anusha

    1. Anonymous (login to see details)

      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

    2. Anonymous (login to see details)

      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.

    3. Anonymous (login to see details)

      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.

  8. Anonymous (login to see details)

    Thank you all for the reply.

    Could you please also let us know the SC command which you tried .

    Regards,

    Anusha

  9. Anonymous (login to see details)

    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.

  10. Anonymous (login to see details)

    Hi All,

    Could you please provide an update on the above issue as its a high priority task for me (sad) .

     

    1. Anonymous (login to see details)

      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

    2. Anonymous (login to see details)

      Hi Anusha,

      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. 

  11. Anonymous (login to see details)

    Thank you all & Brian.

    I will perform the steps provided above .

     

  12. Anonymous (login to see details)

    Hi Brian,

    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.

     

    Regards,

    Rashmi

    1. Anonymous (login to see details)

      Hi Rashmi,

      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"

  13. Anonymous (login to see details)

    Hi Brian

     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.  

    1. Anonymous (login to see details)

      Hi Rashmi,

      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:

      Collector Configuration

       

  14. Anonymous (login to see details)

    Hello,

    The plugin is running indefinitely. What could be the reason?

    Keerti

    1. Anonymous (login to see details)

      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

  15. Anonymous (login to see details)

    Is there a github available for this?

    1. Anonymous (login to see details)

      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

  16. Anonymous (login to see details)

    Hi, has anyone used this Plugin with version 6.5 or 7 ?

    1. Anonymous (login to see details)

      Yes. I have used this, but you can also use the built in Windows Performance Monitor plugin for much of the same uses.

  17. Anonymous (login to see details)

    thx Tarjei. By saying built in you mean metrics given by Host agent? or another plugin, which is Windows Performance Monitoring plugin? Or something else? (smile) 

    1. Anonymous (login to see details)

      If you have a host agent, you should not need to configure the perfmon or any other plugin. 

      then you can solve the problem by using the Infrastructure monitoring:

       

      I would strongly advise you to read up on this section of the documentation:

      https://community.dynatrace.com/community/pages/viewpage.action?title=Infrastructure&spaceKey=DOCDT65

       

      Snippet from that page:

       

      Processes can be monitored by using pattern matching. Click the button to the right of the process name list, then click the top available line in the Pattern column to enter a pattern match string, which must be written in lowercase. 
      The process name to match with the pattern includes the process path. The pattern matching supports * wildcard at the beginning and end.  e.g. *w3wp.exe -ap ".NET 4.5"*

       

      Do note that it requires the pattern to be lowercase

       

      Try doing according to the documentation and report back to me

  18. Anonymous (login to see details)

    ok, instructions are clear, I will test it later on some host, which has agent deployed. But there are some cases, where agent is not deployed and need is very simple, like monitoring windows service state. Is this something what could be done by plugin? like this? https://github.com/Dynatrace/Dynatrace-Windows-Service-Status-Monitor-Plugin

    Where could I get compiled version jar files of it?