Icon

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

Icon

Since Dynatrace AppMon 6.3 the Url  Monitor which is included in Dynatrace AppMon now also provides the possibility to specify timeout for connections.

Therefore for Dynatrace AppMon >= 6.3. and if you don't need the ability to pass a custom header to the server (see version 2.0.0 below) please use the included URL Monitor

Overview

 

This plugin extends the dynaTrace URL Monitor plugin and allows specifying a timeout for connectionsIt's based on a post from the dynaTrace Forum.

Plugin Details

Plug-In Files

version 1.0.0: com.dynatrace.diagnostics.plugins.UrlPlugin

version 2.0.0:

adds possibility to pass a custom header to the server

com.dynatrace.diagnostics.plugins.UrlPlugin_6.3.0.1306.jar

Author

Robert Kühn, T-Systems Multimedia Solutions GmbH

dynaTrace Versions

>= 5.5

License

dynaTrace BSD

Support

Not Supported

Release History

 

Provided Measures

Measure

Description

ConnectionCloseDelay

Required time to close the server connection.

ConnectionTimedOut

1 if the connection timed out, 0 otherwise.

ContentVerified

1 if content verification was successful, 0 if not, no value is provided if content verification is disabled.

FirstResponseDelay

Time elapsed between sending the URL request and receiving the first byte of the response.

HeaderSize

Size of the response header

HostReachable

1 if the HTTP server sent a response in time, 0 if not.

HttpStatusCode

The HTTP status code received from the server mapped to a number.

ResponseCompleteTime

Time elapsed between sending the URL request and receiving the last byte of the response.

ResponseSize

Size of the HTTP response.

SocketTimedOut

Socket Timeout = 1, otherwise 0.

Throughput

Average network throughput achieved during retrieval of HTTP response.

Configuration

Please see the dynaTrace documentation (

Unknown macro: {doclinks} [DOCDT50:URL Monitor]

) for a description of configuration options. Additional configuration options for this version are:

 

Socket Timeout

long

the socket timeout in ms

Connection Timeout

long

the connection timeout in ms

Installation

Import the Plugin into the dynaTrace Server via the dynaTrace Server Settings menu -> Plugins -> Install Plugin. For details how to do this please refer to the dynaTrace documentation:

Unknown macro: {doclinks} [DOCDT50:Plugin Management]
  1. Anonymous (login to see details)

    Hi,

    Just a question regarding the URL Monitor Plugin, when you set up the URL Monitor how would you prevent it from triggering an alert every minute (evaluation timeframe)?

    I would like to configure it to trigger the alert when the URL has breached the allocated threshold and also trigger another notification when it has cleared and not repeatedly.

    Regards

    Katlego

  2. Anonymous (login to see details)

    Hi Katlego

    The URL Monitor itself doesnt trigger an alert. You can define an Incident that is based on the return values of this monitor. The Incident itself has an evaluation timeframe. The Incident also has the notion of "Incident STart" and "Incident End" and wiill only trigger the action upon start.

    Please have a look at Incidents. If you have more questions feel free to post them in the general dynaTrace Open Q&A forum

  3. Anonymous (login to see details)

    We're seeing strange behavior with one of our URL monitors.  We have an old version of the website and a new version of the website.  As standard practice, the old site is decommissioned and has a maintenance page set up.  All requests should be getting redirected to the new site, but what we're seeing is instead the Monitor is actually executing against the old site and returning the maintenance page.  We've done an nslookup on the server and collector machines, both of which point to the new IP address, and going to the page directly in the browser also redirects correctly.  It's just the URL monitor that is stuck going to the old site IP address.  Is there some DNS caching in the collector that would prevent it from updating to the new IP address?

    Thanks!

    Andy

  4. Anonymous (login to see details)

    Hi All , 

    I'm using url monitor to create a monitor to be used by an incident , I want the incident to send an email in case the url isn't working so ,,

    which measure is the best to check the status of url if it's up ?

    Thanks , 

    Saad.

    1. Anonymous (login to see details)

      In one of my last Live Q&A Sessions I implemented exactly that Alert based on a URL Monitor - check it out: https://www.youtube.com/watch?v=Ysh_HL8HDoA&index=11&list=PLqt2rd0eew1bmDn54E2_M2uvbhm_WxY_6

      I think the best is if you use the HostReachable in the combination with the HTTP Status Code. So HostReachable >= 1 && HTTP Status Code <= 200

      Andi

      1. Anonymous (login to see details)

        Hi Andreas,

        Should it be hostreachable: 1 (severe lower limit) and http status code: 200 (severe upper limit and severe lower limit) with logic as AND?

        http://s6.postimg.org/6epqpah0h/hostreachable.png

        http://s6.postimg.org/n3r6l7dlt/statuscode.png

        Thanks,

        Keerti

        1. Anonymous (login to see details)

          Hi. It should be Lower Level 0 for Hostreachable. Why? Becuase you want to be alerted if this value goes to zero or below zero -> thats how the lower severe threshold is evaluated.

          As for HTTP Status Code. Here I suggest you do an HTTP 400 for Upper Server. Why? Because up until HTTP 400 requests are kind of OK - unless you also want to alert on 3xx which are redirects. 

          So - to sum it up:

          • Hostreachable: Lower Severe = 0
          • HTTP Status: Upper Severe = 400

          Andi

           

          1. Anonymous (login to see details)

            Hi Andi,

            Thank you for the reply. Is there a way to get the URL also as a retrieved measure? I am using the extended email plugin and I would like the email body to contain the URL as well.

            Thanks,

            Keerti

            1. Anonymous (login to see details)

              Measures are numeric values that you can chart. We dont return the URL as this would not work with charting

  5. Anonymous (login to see details)

    Thanks a lot Andi ,

    Saad.

  6. Anonymous (login to see details)

    Hi All,

    I'm just trying to monitor whether server is up/down/reachable.. however, I don't have any specific  that I could use for that purpose. Is there any other way to do so by skipping the http request,  I would like dynatrace to use ssh instead to detect whether or not host is reachable

    Thanks for your cooperation

    Emerson

    1. Anonymous (login to see details)

  7. Anonymous (login to see details)

    Thanks Andreas,

    It looks that plugin is not working for dynatrace 5.6, I installed it and it's running forever. do you have any other thought in regards to server monitoring state (up/down)?\

  8. Anonymous (login to see details)

    Hi Andy,

    I am trying to monitor specific server with the URLs, While doing so i'm not getting the proper response from dynatrace plugin. Dyntrace plugin only gives me the first request response which takes 4.58KB & 15.54 ms, whereas browser shows response of 647.88KB & 1.6 Sec.

    Need to know the why this is happening. 

     

    Thanks,

    Sachin

       

    1. Anonymous (login to see details)

      The URL Monitor plugin ONLY downloads the one URL but doesnt download the whole page including all images, js and css files. that explains the difference on what you see in your browser tools. If you want to measure the full page time you could go with this plugin: Web Transaction Monitor Plugin - OR - look into our professional Synthetic Monitoring offering that we have: http://www.dynatrace.com/en/products/synthetic-monitoring.html

  9. Anonymous (login to see details)

    Hi Andy,

    I am using the URL monitor plugin for some urls on our environment. Which was working fine. But for some of the URLs health checks were throwing this error even after 

    Disable certificate validation was enabled.


    Message: SSLPeerUnverifiedException

    SSL handshake failed, this may be caused by an incorrect certificate. Check 'Disable certificate validation' to override this.
    Exception message: peer not authenticated

    Can you help with that.

     

    Thanks,

    Seshi

     

    1. Anonymous (login to see details)

      Seshi,

      This is something we've dealt with before but I agree that the checkbox doesn't seem to disable the validation.  I've had luck with this when I also changed the Protocol to HTTPS when disabling the certificate validation.  The test usually ran just fine after that.  We're running a slightly modified version of the plugin though, so it may not affect your version.

    2. Anonymous (login to see details)

      We got an issue with HTTPS connection after moving to Dyntrace 6.3. We found out that it happened due to the RC4 Cipher being disabled on JRE version 1.8 due to security reasons of it being a weak cipher.

      You can check that information on Oracle JDK-8076221.

      To check the cipher that the URL is using, you can use NMAP Enum Ciphers.

      With the JDK information plus the Dynatrace knowledge, it would be possible to re-enable it by doing the procedure:

      - Edit the file "DT_HOME/jre/lib/security/java.security" (on the collector that runs the URL monitor)
      - Locate "jdk.tls.disabledAlgorithms"
      - Edit it and remove "RC4"
      - Also edit "jdk.tls.legacyAlgorithms" and remove "RC4_128, RC4_40"

      However we tested and it didn't work. From tests with JRE versions, it seems that the latest version that RC4 worked was JRE 1.8.0_45.
      We were able to use the URL monitor by removing the OOTB JRE on the collector installation and re-installing with JRE version 1.8.0-45.

      This is just a workaround to monitor those URLs, however the best approach is to change the cipher on the webserver that you're connecting since it has security issues.

  10. Anonymous (login to see details)

    Thanks Andy

    If you have a modified version. Please share us the updated version. We will be happy bump up over version.

    Please let us know.

    Thanks,

    Seshi.

    1. Anonymous (login to see details)

      Seshi, I'll have to check with the developer and make sure they're OK with it (smile).  Were you able to change the protocol and see if it worked?

      1. Anonymous (login to see details)

        Did somebody ever solve the problem?

        I have the same issue and tried also the disable certificate validation checkbox with https configuration.

        I'm not able to get the stuff running.

  11. Anonymous (login to see details)

    Or it would be helpful to know what keystore this plugin uses so we can import the needed certs.

  12. Anonymous (login to see details)

    Hey

    Are there any way to send host-headers or any other type of headers? We would like to monitor a multi-homes server and use the 'Host' header like this curl example:

    curl -verbose --header 'Host: www.example.com' http://93.184.216.34

     

    Regards

    Henrik

     

    1. Anonymous (login to see details)

      i dont think this is supported in the moment. As the project is open and on github one could add that feature. 

  13. Anonymous (login to see details)

    Hi I have still Problems with TLS 1.2

    I get the following Error message, also when Disable certificate validation is enabled:

    SSL handshake failed, this may be caused by an incorrect certificate. Check 'Disable certificate validation' to override this.

    Exception message: peer not authenticated

     

     

     

  14. Anonymous (login to see details)

    Hi Andy,

    I am having problems with both the URL and SOAP monitors sometimes. The "ResponseCompleteTime" measure is sometimes giving values >2000 ms whereas when I take a look at the purepath response time, the max is around 80 ms. I am very confused with the difference. Can you please explain why the "responseCompleteTime" is sometimes so high whereas the purepath time remains low? 

    Thanks,

    Keerti

    1. Anonymous (login to see details)

      Hi. Can you post this question on the discussion forum? https://answers.dynatrace.com/spaces/148/index.html - i would like more people to benefit from the answer

      1. Anonymous (login to see details)

        Sure Andy! Thanks

  15. Anonymous (login to see details)

    This Community Supported plugin seems to be unnecessary given the URL Monitor plugin delivered with AppMon.  If there's a need for this Community Supported instance, perhaps we should clarify the difference.  The Overview paragraph at the top of this page mentions this version contains a Connection Timeout value, but so does the one that comes with AppMon product.

  16. Anonymous (login to see details)

    I'm having an issue where the URLMonitor is not following a redirection.  All the browsers that I've tested follow the chain of redirections just fine (even on the Collector itself), but the URL Monitor just reports "Status: finished", "Message: NoHttpResponseException", "Last Run Result: incomplete", and the Detailed Message includes "The target server failed to respond."  The URL in the Detailed Message is exactly correct.  

    I've looked at the raw HTTP being returned and the only thing unusual about it is that the response includes a Host header with an internal hostname (not reachable from the collector).  Is the URLMonitor using this Host header value in calculating the redirection target?  (It probably shouldn't be; as I said, none of the major browsers has a problem with this redirection.)

    If I set the URLMonitor to look at the target of this redirection (on the same host), then it works fine.

    Is this a reasonable guess as to the cause of the issue?  Any suggestions for a workaround? (other than to bother the site maintainers to use something like X-Server in the response headers instead of Host)

     

  17. Anonymous (login to see details)

    Is there any way to put in a retry logic where if the url is not reachable or in a desirable state the monitor would immediately retry and if it failed again then generate an alert. So on failure try once again.

  18. Anonymous (login to see details)

    Hi Team,
    URL monitor 6.1 was working fine till date but today I'm getting following exception:

    SSL handshake failed, this may be caused by an incorrect certificate. Check 'Disable certificate validation' to override this. Exception message: peer not authenticated

    Even I checked the Disable Certification validation check-box but issue doesn't get resolved.

    I do have Dynatrace Client 6.1. Please suggest where should I check now.

    1. Anonymous (login to see details)

      Hi. I see you also posted the same question on the forum. I suggest we continue the discussion there: https://answers.dynatrace.com/questions/165562/url-monitor-61-ssl-handshake-failed-error-in-dt-61.html

      1. Anonymous (login to see details)

        yeah sure I didn't get response over there so I posted here also

         

  19. Anonymous (login to see details)

    Hi,

    After some tests, it seems the url monitor plugin does not work for 2-Way SSL communication.

    Could you confirm that ?

    Thanks

  20. Anonymous (login to see details)

    Hi,

    I need to verify one URL with de POST method but my POST Data parameter is in JSON, with the google extension Postman my URL works fine.

    It's possible to do that with this plugin (URL Monitor)

     

    Thanks

     

     

     

    1. Anonymous (login to see details)

      Hi Jose,

       

      when I wrote it's possible to do that with this plugin. Is it regarding 2-Way SSL communication ?

      I set up the following parameters in the dtcollector.ini file :
      -Djavax.net.ssl.keyStoreType=pkcs12
      -Djavax.net.ssl.keyStore=/logiciels/dynatrace/psc-client_edf_fr.p12
      -Djavax.net.ssl.keyStorePassword=xxxxxxxx

      but these parameters are not taken account.

      Do you have a sample ? 

  21. Anonymous (login to see details)

    Is there any way to put in a retry logic where if the url is not reachable or in a desirable state the monitor would immediately retry and if it failed again then generate an alert. So on failure try once again.