Monitor URL to google.com ?!?

yes, you would need to set-up a host that is google.com to do this as the monitor runs against the different hosts. This could also be a good way to test that your site is currently up by setting up www.myapplication.com.

Edit: I would make sure that you are verifying some sort of content on the google homepage something like "I'm Feeling"

Fernando,

Yes, you can use the URL monitor plugin to verify that access to the internet is working.  Note, however, that the plugin is run on the Dynatrace Collector, and so checks connectivity from there.  You could still have a problem, e.g., in other firewall zones if there was a firewall problem.

-- Graeme

Thank you guys,

It worked, after configuring the proxy.

Regards,
Fernando.

Just an FYI for others that may want to do similar things. I covered this exact use case including alerting in one of my perf clinics. find the recoding on our youtube channel: https://www.youtube.com/watch?v=Ysh_HL8HDoA&index=11&list=PLqt2rd0eew1bmDn54E2_M2uvbhm_WxY_6

Andi

I add the host address wrong as https://www.verizon.com, but after correcting it and evening recreating the monitor the collector is still trying to use http://[https://www.verizon.com]/ and throwing an error.  Any ideas on what might be causing the issue?

Here is the text from the log:
Caused by: java.net.URISyntaxException: Expected closing bracket for IPv6 address at index 15: https://[https://www.verizon.com]:443/  at java.net.URI$Parser.fail(URI.java:2829)  at java.net.URI$Parser.failExpecting(URI.java:2835)  at java.net.URI$Parser.parseServer(URI.java:3212)  at java.net.URI$Parser.parseAuthority(URI.java:3136)  at java.net.URI$Parser.parseHierarchical(URI.java:3078)  at java.net.URI$Parser.parse(URI.java:3034)  at java.net.URI.<init>(URI.java... 2015-08-05 18:19:37 WARNING [UserPluginManager] java.lang.IllegalArgumentException - Expected closing bracket for IPv6 address at index 15: https://[https://www.verizon.com]:443/ java.lang.IllegalArgumentException: Expected closing bracket for IPv6 address at index 15: https://[https://www.verizon.com]:443/  at java.net.URI.create(URI.java:859)  at org.apache.http.client.methods.HttpGet.<init>(HttpGet.java:69)  at com.dynatrace.diagnostics.plugin.urlmonitor.UrlMonitor.createHttpMethod(UrlMonitor.java:473)  at com.dynatrace.diagnostics.plugin.urlmonitor.UrlMonitor.execute(UrlMonitor.java:219)  at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:752)  at com.dynatrace.diagnostics.sdk.UserPluginManager.b(SourceFile:489)  at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:285)  at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:51)  at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:26)  at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:190)  at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:413)  at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.execute(SourceFile:337)  at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.a(SourceFile:101)  at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.work(SourceFile:92)  at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.executeJobInfo(SourceFile:241)  at com.dynatrace.diagnostics.scheduling.impl.QuartzJob.execute(SourceFile:45)  at org.quartz.core.JobRunShell.run(JobRunShell.java:202)  at com.dynatrace.diagnostics.scheduling.impl.QuartzThreadPool$WorkerThread.run(SourceFile:788) Caused by: java.net.URISyntaxException: Expected closing bracket for IPv6 address at index 15: https://[https://www.verizon.com]:443/  at java.net.URI$Parser.fail(URI.java:2829)  at java.net.URI$Parser.failExpecting(URI.java:2835)  at java.net.URI$Parser.parseServer(URI.java:3212)  at java.net.URI$Parser.parseAuthority(URI.java:3136)  at java.net.URI$Parser.parseHierarchical(URI.java:3078)  at java.net.URI$Parser.parse(URI.java:3034)  at java.net.URI.<init>(URI.java...

James,

Could you share a screenshot of your monitor configuration, please?  Here's what I think you should have:

Well, now I see that you wanted to use https, so this screenshot is not exactly what you want ...

-- Graeme