Troubleshooting - URL Monitoring
Prerequisites:
- The URL which the customer want to monitor should be accessible from the Machine where the APM is installed.
- Check if the customer have configured any proxy for accessing the particular URL
- If yes, then the same proxy must be configured in the APM too
- If there are headers, request parameters needed they should be configured appropriately
- Add user agent before adding, if required
- Some times websites may be configured to behave differently for different browsers
Troubleshooting:
- Check for the response code returned while accessing the URL. We will expect Response code 200 by default for the every URL
- Refer the link for definitions of various response code: https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
- Ask the customer enable 'Logging for URLs' and poll the monitor, so that response received will be saved as file under 'Debug_Info' folder. We can check for the response code and the response received for the particular URL
- If the URL is not collecting data and if it is SSL configured ask for the version of the SSL used (SSLv3, TLSv1, TLSv1.2, etc)
- If still the issue can't be predicted, then ask the customer to Poll the monitor or reproduce the issue 2 or 3 times and send us a SIF
Hint:
If the URL the customer tries to monitor is a Public URL then we can try adding the same URL here and check the issue.
New to ADSelfService Plus?
Related Articles
Troubleshooting URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Monitoring HAProxy - Configuring the HAProxy Stats page
To monitor a HAProxy instance: Open the 'stats' port for collecting the metrics. To enable metrics collection, add the following content at the bottom of the file /etc/haproxy/haproxy.cfg: listen stats :9000 mode http stats enable stats hide-version ...Troubleshooting SSL Handshake Error
SSL Handshake Error SSL Handshake error occurs when a secure connection cannot be established to the URL added for monitoring. Common reasons for it are wrong SSL protocol version, incompatible ciphers, and invalid/missing client-side certificate. ...AWS EKS Troubleshooting FAQs
AWS EKS monitor can be configured only if you have already added an Amazon monitor in Applications Manager. Ensure that you have met the pre-requisites for the Amazon monitor before monitoring Elastic Kubernetes Service in Applications Manager. How ...