cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Content verified Monitoring configuration Issue

sathwika_vatte
Inactive

content-verified-configuration1.pngcontent-verified-configuration2.pngcontentverified-measure.png content-verified-configuration.png

Hi,

Last two days we are having a trouble with our login Page. Issue is server is responsive but login page doesn't show up. So, we want to setup an alert if login page doesn't show up. We are trying to setup URL monitoring by using content verified measure. Task itself failing with error message:"Executing monitor failed". I don't know what i am missing in configuration. i attached all configuration part screenshot and details about error message screen shot, Please find them as attached to this question.

Thanks,

Sathwika

3 REPLIES 3

Joe_Hoffman
Dynatrace Leader
Dynatrace Leader

The monitor executes on the specified collector. Can you verify that the collector has access to the target URL?

I would work initially to verify your monitor can run against a simple URL, maybe http://yahoo.com/ (assuming it's reachable from the specified Collector).

Each Monitor writes out a log file on the collector machine where it is configured to run. Check to see if the log/ directory on that collector contains any logs from this monitor. Depending on how catestrophic the failure, there might not yet be any logs.

hth

joe

sathwika_vatte
Inactive

HI joseph,

Thanks for reply

i checked the logs related to URL monitoring, i found error message that connection refused between the URL and collector(Logs copied below). then checked collector connections it is up and running,and capturing data. But we have another in collector is jvm java8 was deleted it needs to be re-install. I am assuming this is the root cause for URL monitoring failing. Please share you thoughts.

Logs:

2017-07-18 19:56:55 WARNING [UserPluginManager] org.apache.http.conn.HttpHostConnectException - Connection to https://URL refused

org.apache.http.conn.HttpHostConnectException: Connection to https://URL refused

at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:158)

at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149)

at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)

at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:573)

at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425)

at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)

at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)

at com.dynatrace.diagnostics.plugin.urlmonitor.UrlMonitor.execute(UrlMonitor.java:245)

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

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

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.ConnectException: A remote host refused

Thanks,

Sathwika

Joe_Hoffman
Dynatrace Leader
Dynatrace Leader

I'm not sure I understand. But a JRE is required to run a collector, so not sure how you're running a collector if Java was deleted from the collector host.