如何解决Appdynamics监控URL /页面可用性
我正在尝试使用Appdynamics监视页面可用性
我有一台具有一个站点和多个应用程序的IIS服务器。
在受监视的服务器上安装了Appdynamics .Net代理20.4.1
每个应用程序都有一个appName.svc网页,我可以调用该网页来检查服务是否启动。
我正在尝试AppDynamics Extension for URL Monitoring
并按照安装说明进行操作。
我可以在Metric browser
的“ URL监视器”部分中看到“度量标准已上载”。
我在哪里可以看到URl处于关闭/打开状态?
可以像在yml文件中一样监视多个URL?
sites:
#No authentication,with a pattern to match
- name: ReportService.svc
url: https://serverName/Reports/ReportService.svc
followRedirects: false
groupName: MySites
- name: DigitalService.svc
url: http://serverName/Digital/DigitalService.svc
followRedirects: false
groupName: MySites
- name: EmailService.svc
url: http://serverName/Email/EmailService.svc
followRedirects: false
groupName: MySites
日志:
[Monitor-Task-Thread1] 29 Aug 2020 11:04:05,831 ERROR URLMonitorTask-URL Monitor - Unexpected error while running the URL Monitor
com.singularity.ee.agent.systemagent.api.exception.TaskExecutionException: java.lang.NullPointerException
at com.appdynamics.extensions.urlmonitor.config.RequestConfig.setClientForSite(RequestConfig.java:71) ~[?:?]
at com.appdynamics.extensions.urlmonitor.URLMonitorTask.run(URLMonitorTask.java:79) [?:?]
at com.appdynamics.extensions.TasksExecutionServiceProvider$1.run(TasksExecutionServiceProvider.java:48) [?:?]
at com.appdynamics.extensions.executorservice.MonitorThreadPoolExecutor$TaskRunnable.run(MonitorThreadPoolExecutor.java:113) [?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_241]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_241]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_241]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_241]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_241]
Caused by: java.lang.NullPointerException
at com.appdynamics.extensions.urlmonitor.config.RequestConfig.setClientForSite(RequestConfig.java:55) ~[?:?]
... 8 more
[Monitor-Task-Thread1] 29 Aug 2020 11:04:05,831 INFO URLMonitorTask-URL Monitor - All tasks for URL Monitor finished
[Monitor-Task-Thread1] 29 Aug 2020 11:04:05,831 INFO MetricWriteHelper-URL Monitor - Finished executing URL Monitor at 2020-08-29 11:04:05 IDT
[Monitor-Task-Thread1] 29 Aug 2020 11:04:05,831 INFO MetricWriteHelper-URL Monitor - Total time taken to execute URL Monitor : 0 ms
[Monitor-Task-Thread1] 29 Aug 2020 11:04:05,831 INFO ABaseMonitor - Finished processing all tasks in the job for URL Monitor
[pool-10-thread-2] 29 Aug 2020 11:04:09,628 INFO MetriclimitCheck-URL Monitor - Starting MetriclimitCheck
[pool-10-thread-2] 29 Aug 2020 11:04:09,628 INFO PathResolver-URL Monitor - Install dir resolved to C:\Program Files\AppDynamics\machineagent
[pool-10-thread-1] 29 Aug 2020 11:04:09,628 INFO MachineAgentAvailabilityCheck-URL Monitor - Starting MachineAgentAvailabilityCheck
[pool-10-thread-1] 29 Aug 2020 11:04:09,628 INFO MachineAgentAvailabilityCheck-URL Monitor - SIM is enabled,not checking MachineAgent availability metric
[pool-10-thread-2] 29 Aug 2020 11:04:11,175 INFO MetriclimitCheck-URL Monitor - MetriclimitCheck took 1547 ms to complete
[pool-10-thread-2] 29 Aug 2020 11:04:29,629 INFO MetriclimitCheck-URL Monitor - Starting MetriclimitCheck
[pool-10-thread-2] 29 Aug 2020 11:04:29,629 INFO PathResolver-URL Monitor - Install dir resolved to C:\Program Files\AppDynamics\machineagent
[pool-10-thread-2] 29 Aug 2020 11:04:31,332 INFO MetriclimitCheck-URL Monitor - MetriclimitCheck took 1703 ms to complete
[pool-10-thread-1] 29 Aug 2020 11:04:49,629 INFO MetriclimitCheck-URL Monitor - Starting MetriclimitCheck
[pool-10-thread-1] 29 Aug 2020 11:04:49,629 INFO PathResolver-URL Monitor - Install dir resolved to C:\Program Files\AppDynamics\machineagent
[pool-10-thread-1] 29 Aug 2020 11:04:51,254 INFO MetriclimitCheck-URL Monitor - MetriclimitCheck took 1625 ms to complete
解决方法
总结:
- 问题未包含完整的 config.yml 内容
- 许多默认配置需要如下注释
# Patterns to be matched,multiple patterns(to be matched) can be configured for a given site #matchPatterns: #- name: # type: # pattern: #- name: # url: # authType: # Basic Authentication with password encryption #- name: # url: # username: # password: # encryptionKey: "" # encryptedPassword: "" # authType: #- name: # url: #NTLM Auth Sample Configuration #- name: # url: # username: # password: # authType: # Client Cert Auth Sample Configuration #- name: # url: # password: # authType: # keyStoreType: # keyStorePath: # keyStorePassword: # trustStorePath: # trustStorePassword: #POST request sample configuration #- name: # url: # username: # password: # connectTimeout: 60000 # usePreemptiveAuth: # method: # headers: # Content-Type: application/json # requestPayloadFile: src/test/resources/conf/postrequestPayloadFile # matchPatterns: # - name: Error # type: substring # pattern: Error 400 #Proxy Configuration #- name: # url: # groupName: # proxyConfig: # host: "" # port: # username: "" # password: ""
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。