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


The availability monitor can be used to test if a server can be pinged, and will also check to ensure that DNS and reverseDNS capabilities are functioning.

Plugin Details

Plug-In Versions

Availablity Monitor Plugin 1.0.0 (compatible with dynaTrace >= 5.5)

Availablity Monitor Plugin 1.2.0

Availablity Monitor Plugin 1.2.1

Availablity Monitor Plugin 1.2.3


Derek Abing: version 1.0.0

Praveen Begur (Dynatrace): version 1.2.0

Renato Puccini: version 1.2.1

Jeroen Hautekeete (Dynatrace): version 1.2.3


dynaTrace BSD


Community Supported

Known Problems


Release History

2013-03-12 Initial Release
2013-04-18 Updated Plugin

2016-01-21 version 1.2.0

2018-02-02 version 1.2.3

Version 1.0.0

Provided Measures

DNS Resolved: Returns a 1 if the server DNS name is resolvable and a 0 if the server is not resolvable
 Ping Check: Returns a 1 if the server is pingable and a 0 if the server is not pingable
Reverse DNS Resolved: Returns a 1 if the server DNS name is resolvable and a 0 if the server is not resolvable
TCP Check: Returns a 1 if the server is reachable on TCP port 7 and a 0 if the server is not reachable
TCP Lock Time: Returns the time taken to secure a Socket Lock on TCP Port 7




Max TCP Return Time

The max allowed time for the response to the ping in ms


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

Version 1.2.0

Changes compared to version 1.0.0

  1. Removed most of the existing metrics since I found them difficult to interpret and replaced them with metrics named as xxx_violation.
  2. The plug-in provides two high level metrics for an IT Manager – a) Availability and b) Violation. Availability can either be 0% (something that we are expecting is not working) or 100% (All Green). Violation is num of times Availability is less than 100% (i.e zero %) during a single execution for some technical reason. These metrics help in creating an overall IT manager SLA dashboard showing overall Avail and No of Violations of 100% Avail in a day or week etc.   
  3. Additional metrics named as xxx_violation are provided for specific reasons for overall Availability being less than 100% - Errors like DNS failure, reverse dns failure, ping failure, tcp connect etc.
  4. Added properties/Boolean flag to make ReverseDNS Test and Ping Test as optional. This was required since earlier plug-in made these tests mandatory with-out giving a choice to the user. Many DC’s disallow Ping and hence Ping test would fail. Reverse DNS Look-up may not work in some DC’s and hence this would fail as well.


  1. Configure the monitor with target host (as usual) and choose if Ping and Reverse DNS Tests are required or not.
  2. Create Line or Bucket Chart for Availability (aggregation=average)
  3. Create Bucket Chart for Violation (aggregation=sum). This tells us how many times in a day was Avail found to be less than 100%.
  4. Create Bucket Chart for the other Violations like TCP Connect time / DNS / Reverse DNS / Ping etc.
  5. Note: If more than one type of failure happens – for example Reverse DNS and PING fail, the overall Violation count is still ONE, Avail=100% and individual violations of ReverseDNS and Ping are set to ONE each.


Version 1.2.2 - unreleased


  1. Fixed availability evaluation, where unreachable hosts remained unreachable until next collector restart

Version 1.2.3


  1. Added workaround for incorrect result of InetAddress.isReachable() on Windows hosts


#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))


  1. Hello,

    i can´t choose the measure "Ping max " after Installation. Can you help me?

    Best Regards from Berlin Germany


  2. Hi,

    The ping avg, min, and max measures have actually been removed from the plugin. I'll have Compuware update the page to reflect this. If you really want this information I can get them added back into the plugin.



  3. Hi,

    I'm relatively new as to how you download the plugin and configure it and also how to create the measures. May you please give me a quick crash course as how to configure it and deploy it.




    1. Have a look at the following doc page: Plugins

      After you have installed the plugin you can open your System Profile and Create a new Monitor in the section that allows you to configure Monitors. Once the monitor is configured it will be executed in the specified interval (=schedule) for each host (or list of hosts) that you have configured. The monitor will then generate result measures that you can use for charting or for Incidents.


  4. Hi , 
    I'm facing an issue that Ping check measure returned "1" when the server isn't Pingable , the situation as follow ,
    I tried to ping the server manually so I get Destination Host unreachable .
    but when the result is request timed out ping check returns 0
    Could you help in that ? 
    1. I pinged the author of the plugin about this. I hope he finds time to have a look at your comment.

      As all our community plugins are available on GitHub you can also have your own look at the source code and check what might go on in this case.

  5. Are you saying that the ping measure returns a 1, meaning successful, even though when you ping the server manually it isn't returning a ping? Are you pinging it through a command prompt?

  6. Hi Derek


    Looks like this plugin will not work correctly on a linux collector/dt server environment running 6.1

    For some reason the monitor will run forever.  If you stop it then it will report it as successful.


    Any new version coming out soon?

  7. Hi David,

    Unfortunetly, we are not running 6.1 at the moment so I won't be able to update the plugin until this Spring after we update to whatever the Spring release is.

    1. I am assuming you are not having this issue in the 5.5

      Any thoughts on why my issues is happening?

  8. Hi Derek,

    I am trying to use the plugin on a 5.6.6203 Linux dT Server/Collector system, but it doesn't seem to start executing, and I get no logs generated. Does it work with Linux systems?




  9. Hi,

    I'm trying to alert on when a particular server is down. 

    When I chart the measure (aggregation set to minimum), I see I'm getting a '1' for the ping check when the server is restarted - I've set the monitor to run every 10 seconds and the server takes about 1min from shut down to start up. I see Saad had something somewhat similar, any word on that? 

  10. Yes Kayan ,

    I was trying to alert the exact situation but unluckily it doesn't work for me since this monitor it works only in specific situations and it gives 1 in at least 2 situations while the server is down or unreachable , I think it needs to be updated by the owner .


  11. HI,

    I'm using the plugin for 5.6 and the monitor is runing forever, then when I stop it says that last run was as successful. Also, I can't delete the monitor from dynatrace console either. it looks like this plugin is not working for dynatrace 5.6 either




  12. Hi,

    I'm using Dynatrace 6.2 and the plugin is not working properlly.

    It says the address is not reachable, but I can ping it.


    2016-02-11 15:24:32 SEVERE [AvailMonitor@cca4750c-5426-4a3c-bb51-92311d571458] Not reachable address:


    The problem might be related to what says in this website: but I'm not sure.


    Anyone having the same issue?

  13. This appears to not be working in is this also the case with versions newer such as 6.3? I can ping a server from my collector no problem, the plugin says it finished with incomplete results. The ping violation number just keeps increasing, started at 1 and goes up by one every time it was ran, and says availability is 0.


  14. Seems to happen to me too. (Version 6.3)

    If I use the monitor in a fully Linux environment, it works.

    If the collector is Linux and the agent is windows, this Host Availability monitor does not work. 

    Same with windows collector and windows agent.


  15. We have availability monitors that have been running on 6.0 for over a year that worked great. Since the upgrade to 6.3.1, the IP addresses no longer resolve to the server name in the dashboard and the dashboard displays IP addresses. We also have TCP port checks running in the same system profile. collector and dashboard, and do not see this issue with the TCP port checks. Any ideas?

    1. Anything in the plugin logfiles on your collector? 

      1. Not that I can tell. This entry keeps repeating itself.

        Caused by: Connection timed out: connect

        at ...

        2016-04-04 09:43:37 WARNING [UserPluginManager] - Authentication failed. Authentication failed.

        at com.dynatrace.diagnostics.plugins.vmstat.connection.SSHConnectionMethod.connect(

        at com.dynatrace.diagnostics.plugins.vmstat.connection.SSHConnectionMethod.setup(

        at com.dynatrace.diagnostics.plugins.vmstat.connection.SSHConnectionMethod.setup(

        at com.dynatrace.diagnostics.plugins.vmstat.VmstatMonitor.configureConnectionMethod(

        at com.dynatrace.diagnostics.plugins.vmstat.VmstatMonitor.doSetup(

        at com.dynatrace.diagnostics.plugins.vmstat.VmstatMonitor.setup(

        at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:645)

        at com.dynatrace.diagnostics.sdk.UserPluginManager.b(SourceFile:436)

        at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:278)

        at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:50)

        at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:26)

        at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:190)

        at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:413)

        at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.execute(SourceFile:337)

        at com.dynatrace.diagnostics.schedule.SchedulerJob.a(SourceFile:101)


        at com.dynatrace.diagnostics.schedule.SchedulerJob.executeJobInfo(SourceFile:241)

        at com.dynatrace.diagnostics.schedule.QuartzJob.execute(SourceFile:45)


        at com.dynatrace.diagnostics.schedule.QuartzThreadPool$

      2. During an upgrade, are there ini or XML files for plugins that we should check on the collector to make sure they are in the upgraded directory?

  16. Hello,


    a good enhancement for the plugin is that we have to choose the port it will be tested the telnet command instead of the port 7. It would help to check communication availability before getting errors on app side.


    1. I did an improvement by having the option where we can set up connection port to be tested.

      Attached is a parallel version of the plugin.


  17. Hi,

    I am able to ping a host from a collector machine successfully. But when I ping the same host from the same collector using this monitor (version 1.2.0), it is giving availability as 0. I have set the logs to 'finer' but all the logs recorded is the below message:

    2016-05-03 11:05:01 SEVERE [AvailMonitor@VSG Collector_0] Pinging Failure : ping Args:  -w 5

    Note: I am using Dynatrace 6.2.

    Thank you,


  18. Hello,

    I am having the same issue as some of the users above. I can ping the host from a collector machine successfully, but using the monitor returns a ping violation. Has there been any progress on this issue?

    Using Dynatrace 6.3.



    1. Hello,

      I have the same problem, did you find any solution yet?


      1. Birtan,

        Unfortunately, no. I have just been using the TCP check in the meantime.

  19. Hi Renato Puccini

    I'm having the same issue as those above with Dynatrace 6.3 and the latest version of the plugin, 1.2.1.  A Netmon capture shows the same as others have seen, that the plugin fails internally and does not generate the ping whereas a manual ping from the same server using the same arguments is successful.

    Are you able to look at the plugin and update please?



  20. Hi,


    Question: Since this is sending a ICMP packet to test.  Why do I have to specify a TCP port in the configuration setting of the monitor?  What should I put here?

    1. Hi John,

      the plugin also checks if the server is reachable on tcp port 7 if you set "Enable TCP Check" to true.

      TCP Check: Returns a 1 if the server is reachable on TCP port 7 and a 0 if the server is not reachable



  21. Also how did you get the dashboard, the one in the picture?

  22. Hello guys,

    I am also having Ping issue with this plugin. Anyone please let me know where is the problem. Please see below my post further description:


  23. Availability monitor 1.0.0 is failing for a few servers(intermittently) even though the server is up and running without any issues.
    Any issues for Dynatrace 6.5 with the plugin?

    Host Availability Monitor 1.2.1 is completely failing with the reason "Error during execution of plugin occurred".

  24. Deployed this Monitor plugin (version 1.2.1) and upon first try received the error message "Error during execution of plugin occurred".

    2017-05-11 12:16:20 WARNING [UserPluginManager@Host Availability_2] java.lang.NumberFormatException - For input string: ""
    java.lang.NumberFormatException: For input string: ""
        at java.lang.NumberFormatException.forInputString(
        at java.lang.Integer.parseInt(
        at java.lang.Integer.parseInt(
        at com.mycompany.myplugin.AvailMonitor.execute(

    The root cause of the issue was that we left the TCP Port (String) field blank.  Since the plugin is attempting to parse the String and obtain an int, it cannot get an int from a String = "'.  So if you are not using the TCP Port check, put any numeric value in the TCP Port field and it should work.