Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
11-26-2017 12:14 AM
Hello,
I've instrumented .net application in App'd, I've got below critical business transactions configured
1.Enroll,
2.Reset,
3.Forgot password,
4.Unlock
I'm able to receive multiple BT calls, but i receive some dynamic user request in BT calls, but i shows more no of business transactions in the list and it look so congested., How can i sort out this., should i exclude that BT or should i create any rule to conisder it as single Business transactions.
Regards,
Soundarajan
11-27-2017 10:18 AM
Hi,
First thing to check is how your BT detection rule is configured?
The default for asp.net or WCF call marks or records a unique BT as service.operation name, for other calls, its the number of URI segments. I would suggest you check that first and make sure the configuration is the way you want.
Next step, if you see more than expected BTs, you can do either a grouping or write exclude rules to exclude certain types of BTs.
https://docs.appdynamics.com/display/PRO44/Organize+Business+Transactions
Thanks,
Gurmit.
11-28-2017 10:33 PM
Hi Sundar,
Please follow the steps shared by Gurmit and let us know if face any issues.
In case if you still face the issue -
* Please share screen shot of the list of BTs getting identified and also highlight the section which is problematic.
* Please let us know if the instrumented application is ASP.Net based or you have configured custom match rule ?
* Please share screenshot the rules which you created for those 4 BTs for our review.
12-04-2017 09:34 PM
12-04-2017 11:18 PM
Hi Sundar,
To understand and answer your question "Is it possible to group those dynamics BT's as single BT call?".
Could you please provide us the screenshot of the BT list view and highlight the BTs, which you want to group as a single BT.
Thanks,
Ashish.
12-05-2017 12:49 PM
I think this is because we have selected complete URI as a business transaction.
If you can identify how many segments of the URI form a unique BT then you can use that or the other option is to have a custom match rule to identify those user related transactions and only detect them as a single transaction.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form