All Other Traffic

[CommunityUser]

Hi,

how can i create a seperate business transaction using an entry in All Other Traffic?

Regards,

Nick S.

[Arun_Dasetty]

Hi Nick,

It looks you hit BT limit and hence you are seeing your target BT under All other traffic, resolution is to exclude BTs that you are not interested in "Business transaction" screen and disable rules (auto discovery or split custom rules if any) that leads to more BTs discovery resulting in other load in "All Other traffic -<tier>" BT and once the BT limit is under controller you will start seeing the BTs under Other traffic BT in discovered BT list, Please go through the followng doc links to implement the steps suggested in more detail:

https://docs.appdynamics.com/display/PRO39/Organizing+Traffic+as+Business+Transactions

https://docs.appdynamics.com/display/PRO39/Configure+Business+Transaction+Detection

https://docs.appdynamics.com/display/PRO39/All+Other+Traffic+Business+Transaction

Regards,

Arun

[CommunityUser]

Hi Arun,

Thanks for your reply.

If I exclude to reduce number of transactions to below 50, the All Other Traffic is still the same.

I want to move a transaction from All Other Traffic into the main list, is this possible?

If I reset the agent, will all the historical transaction statistics be lost?  I want to retain historical statistics.

Is there a way to start the BT discovery process from scratch without losing historical statistics?

Regards,

Nick S.

[Arun_Dasetty · Accepted solution]

Hi Nick,

Once BT limit reached "All Other Traffic -<tier>" BT will be created and this BT will exist for ever and cannot be deleted. 

What we are suggesting here once you have the BT limit 50 at agent node level and less than 200 at application level is in control the new load on BTs under "'All Other traffic -<tier>" will start falling under discovered Business transaction screen automatically. Hope that clarified product behavior.

Please find our response to your queries inline:

>>>>>> I want to move a transaction from All Other Traffic into the main list, is this possible?

Answer: Yes, it is possible but not directly, as stated above say: you have 202 BTs discovered hitting app level limit 200. Now you have excluded 40 BTs and the total BTs in BT grid is 160 only and now if you generate load on BT/URLs(refer View traffic details popup in other traffic BT dashboard top right section)  under "All other triaffic -<tier>" BTs , it wil now discover in "Business transaction" screen but this will take few minutes , to speed up the process do an agent reset under Node dashboard -> Agents section by clicking "reset" button to make sure the excluded BTs taken in to affect and the BT limit is reset.

>>>>>> If I reset the agent, will all the historical transaction statistics be lost?  I want to retain historical statistics.

Answer: We understood that you are referring to "reset" button operation under node dashboard , we confirm this will not purge any BT performance data in UI it will just reset BT limit at agent node level in the context of BT detection.

 >>>>>> Is there a way to start the BT discovery process from scratch without losing historical statistics?

Answer: Yes, you can exclude (select exclude transactions option on BT selected from context menu) the unwanted BTs (when ever you want to see BT stats for excluded you can just do unexclude from More actions menu in BT grid) and disable the auto discovery aggressive rules from Configure -> Instrumentation -> transaction detection (say disable servlet auto discovery checkbox) screen and define custom rules that groups multiple requests so that you will see all matching requests under one BT name (ex: rule URI contains SampleApp  now all requests with URI /SampleApp/ /SampleApp/test will be considered as single BT) 

Let us know if that answers all your queries. Please go through the doc earlier provided for steps to do exclude , define custom rules for the same.

Regards,

Arun

[CommunityUser]

Thanks Arun, that answers all my queries.

So what I am doing is to exclude all transactions and then unexcluding the ones I'm interested in, this seems to be working to keep below limit and have visible all the transactions I'm interested in.

Please let me know if there is a better approach.

Regards,

Nick S.

[Arun_Dasetty]

Hi Nick,

Glad to hear that suggestions made have helped. We already suggested better options when the BT limit raised, but we would recommend to take necesaary steps before you reach BT limit to make sure you do not miss any BTs that you are interested in fallen under other traffic for period you want to diagnize in future by doing following steps:

a) Before you genrate load on server once agent configured make sure you analyze whether the default servlet and other entry point auto discovery settings will result in BT limit 50 at node level and 200 at app level as per your webapp requests

b) disable/modify auto discovery for servlet and disable for other entry points auto discovery under Configure -> transaction detection screen if you see that default setting might be aggressive for your environment

c) define custom rule that groups different URI or ws or actions as per your requirement so that you will not hit BT limit ever

Hope that informations helps.

Regards,

Arun