Capturing complete URL of the transactions being performed on the app server
By adding the config webtransaction.naming.use.requesturl=true in apminsight.conf file, the agent will start collecting the complete URLs of the transactions being performed.
This option will be helpful when you have multiple virtual hosts configured on the same app server. You will be able to differentiate which host performs the transactions.
New to ADSelfService Plus?
Related Articles
How to capture complete URL of transactions performed on application server?
By adding the below option in apminsight.conf file, the agent will start collecting the complete URLs of the transactions being performed. webtransaction.naming.use.requesturl=true This option will be helpful when you have multiple virtual hosts ...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 ...How to resolve 403 Forbidden error when accessing Apache Server-status Page?
If you are receiving a 403 Forbidden error when trying to access the Apache server-status page, it's likely due to missing or incorrect configurations in your Apache server settings. The server-status page provides valuable information for monitoring ...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 ...Troubleshooting Bad Request and Internal Server error
When a server responds with a Bad Request (400) or Internal Server Error (500), It typically indicates issues with how the request is being made or processed. The reasons for these errors can vary, but the most common causes are Incorrectly formatted ...