How to generate a URL Debug Tool Response for troubleshooting?

How to generate a URL Debug Tool Response for troubleshooting?

The URL Debug Tool in Applications Manager helps you analyze and troubleshoot the performance of URLs and their components on webpages. It executes the URL, collects performance data, and provides detailed reports for further analysis.

Follow the steps below to generate a URL Debug Tool report:
  1. Log in to your Applications Manager dashboard.
  2. In Applications Manager, Go to the Settings tab -> under Tools -> Click Self Help Tools -> URL Debug.
  3. From the Monitor Name dropdown:
    1. If the resource is already added as a monitor: Choose the monitor name from the dropdown under the respective monitor type.
    2. If the resource is not added as a monitor: Select New Monitor from the dropdown.
  4. Choose the Monitor Type for the Hostname and Port you wish to debug.
  5. If you have selected New Monitor, provide the necessary service details, similar to how you would add a monitor.
  6. Click on the Execute button to fetch the Response of API/URL and perform the debugging.
  7. Applications Manager will collect the URL response and once the data is collected, you will see the URL Connectivity Details and its Response.
  8. For error response, Hover the Failed text under Connectivity column to view the error message.
  9. To view the webpage content and more detailed information, click the Expand icon under the WebPage Content header. You can also copy the webpage content using nearby Copy icon.
  10. To download the URL Debug report, click the Download icon at the top-right corner of the table displaying the results. The report will be downloaded in a PDF format you can save for later analysis.


Share the Report for Further Troubleshooting
To help the Applications Manager support team with troubleshooting, follow these steps:
  1. Take a screenshot of the configuration page (where you selected the monitor and executed the debug).
  2. Share the configuration page screenshot along with the downloaded URL debug report with the Applications Manager support team.
Warning
Please be aware that the Webpage Content section in the URL Debug Tool report may contain sensitive information. Before sharing the report with the Applications Manager support team, make sure to review and verify that no confidential data is included.


                  New to ADSelfService Plus?

                    • Related Articles

                    • Troubleshooting URL Monitor

                      When configuring a URL monitor in Applications Manager, you might encounter several errors related to accessibility, configuration, or server-side issues. Below are common errors along with step-by-step troubleshooting instructions to help you ...
                    • Real User Monitor (RUM) - Troubleshooting

                      If the monitor has not polled data for a long time, follow the below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...
                    • Prerequisites - URL Monitoring

                      Prerequisites: Ensure that the URL you want to monitor is accessible from the machine where Applications Manager is installed. Check if the proxy is configured in Machine/Browser for accessing the URL. If so, the same proxy settings must be ...
                    • Troubleshooting Server error responses

                      When encountering the following server error responses—Bad Gateway (502), Service Unavailable (503), and Gateway Timeout (504)—it typically indicates issues with the server hosting the URL. Troubleshooting Review your server's access logs for the 30 ...
                    • REST API Monitor Troubleshooting Guide

                      Whether you're adding a new REST API monitor or troubleshooting an existing one, the following steps can help resolve common issues. Troubleshooting 4xx Error Codes (e.g., 401, 403) Check Request Configuration: Verify that the correct HTTP method ...