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

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?

Anonymous (login to see details)

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

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.

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.

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.

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?

Anonymous (login to see details)

Anonymous (login to see details)

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.

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)

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.

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

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.