How to capture complete URL of transactions performed on application server?

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 configured on same app server. You will be able to differentiate in which host the transactions are performed.

                  New to ADSelfService Plus?

                    • Related Articles

                    • 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 ...
                    • 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 ...
                    • How to capture username in Real User Monitor using Custom API?

                      Custom APIs in Real User Monitor serve various functions, such as setting dynamic values for user IDs, capturing JavaScript (JS) errors, specifying session timeout, and more. They enhance user session tracking in Real User Monitor, providing a more ...
                    • 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 ...