What's the most effective way to groom BTs once the 50-BT limit is reached?

[CommunityUser]

I'm running the most recent version of the AppDynamics controller in an on-premise environment. As such, I suppose I could up the BT limit of my agents past 50, but no matter what limit I set, my application will likely push it: Our URLs are dynamic enough that I'll surely miss patterns along the way.

How do I best groom my BT list? Is it as simple as identifying URL patterns, setting up custom match rules, and deleting the narrower versions of those BTs until the match rule detects traffic?

[Arun_Dasetty · Accepted solution]

Hi ctiwald,

Yes, setting up custom match rules, and deleting auto discovered BTs will narrow the those BTs until the match rule detects traffic,

- you need to disable Auto discovery of transactions under Configure -> transaction identificcation -> By default (say you are making servlet requests) Servlet entry is enabled -> and also Auto discovery of transactions enabled (disable only auto discovery with servlet entry point still enabled),

and now delete the auto discovered rules and define custom rules as per your requirement

Please refer the sample example and define custom rules as per requirement:
- your application had url requests that starts with /WSApp/ as the start segment and varrying second and third segment as follows:
Login requests:
- /WSApp/account/edit
- /WSApp/account/view/1

- /WSApp/account/delete/1

Item view requests:

- /WSApp/item/edit/3

- /WSApp/item/edit/4

- /WSApp/item/save/5

So you define custom match rule by name "Login Request" with URI option values contians "/WSApp/account/"
and the same for "Item requests/service" for to match request with URI contains "/WSApp/item/"

refer doc:

http://docs.appdynamics.com/display/PRO12S/Configure+Transaction+Detection

http://docs.appdynamics.com/display/PRO12S/Default+Business+Transactions

Thanks,

Arun