cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Get a full URL of a slow Transaction Snapshot

Arsenii.Shub
Wanderer

Hello, is there a way to see the full URL of a particular slow Transaction Snapshot? I believe that some of the slow search requests in our system could be caused by a specific user input that is a part of the dynamic URL. But in the Transaction Snapshot dashboard (or in the Transaction Snapshot overview), I only see the aggregated short URL without a user input.

Full URL example: https://host/Search/userInput

Transaction Snapshot dashboard:

ArseniiShub_1-1703055410781.png

 

Individual transaction overview:

ArseniiShub_0-1703055328778.png

 

Also, I don't think I have access to the Analytics dashboard.

1 REPLY 1

MARTINA.MELIANA
AppDynamics Team

Hi @Arsenii.Shub ,

Thank you for posting on community. I saw you raised a support case already for this. Hence, I would like to share what was the solution, result of my experimentation, and additional information.

Issue: The URLs shown in BT/Transaction Snapshots are incomplete.
Goal: Differentiate slow search requests in the system caused by specific user input.
Tests: I tested the URL behavior on a .NET MVC web app.

Solutions:

  1. URL Display on URL Column:
  2. Complete URL Display on BT name Column:

Next Steps:

For Partial URL in URL column /Search/userInput:

  1. Add App Server Agent Configuration.
  2. Set the following .NET Agent Configuration properties to false:
    • aspdotnet-core-naming-controlleraction
    • aspdotnet-core-naming-controllerarea
       

      Screenshot 2024-07-26 at 17.22.27.png
  3. Restart the AppDynamics.Agent.Coordinator_service and IIS in the same sequence. After that, apply loads and check the BT/Snapshot if necessary.

For Complete URL in BT name https://host/Search/userInput:

  1. Navigate to Configuration > Instrumentation > Transaction Detection in your Application.
  2. Add New Rules:
    • Choose Include, proper Agent type, and Current Entry Point.
    • Fill in the Name Field (it will be shown on your BT).
    • Set Priority higher than Default Automatic detection for prioritization.
       
      Summary.png

  3. Rule Configuration:
    • Matching condition: URL is not empty
    • Custom Expression:
      ${HttpRequest.Scheme}://${HttpRequest.Host}${HttpRequest.Path}${HttpRequest.QueryString}
    • V_Split_Transactions_Using_Request_Data.png

       

  4. Restart the AppDynamics.Agent.Coordinator_service and  IIS in the same sequence. After that, apply loads and check the BT/Snapshot if necessary.

Final Result:

Pasted_Graphic_10.png

image.png

 

Additional Information:

  • You can also add the custom expression by modifying the default Auto detection rule instead off Add new one like how I did in the step above. Result from modifying the default auto detection below.
     

     

    Screenshot 2024-07-29 at 10.19.40.png

Ask the Experts Session: Hybrid Application Monitoring Deployment

Join us on Feb 26 to explore Splunk AppDynamics deployment strategies, SaaS models, agent rollout plans, and expert best practices.


Register Now

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here