AppD Archive

All other traffic

CommunityUser
Splunk Employee
Splunk Employee

Hello,

I have just starting evaluating your software and there is something puzzling me. I have a J2EE application, with many beans/service. I have configured EJB with auto discovery Bean.method and it seems to work pretty well, but it does not include all beans that I know are marked @Stateless... It seems all of these Transactions are pooled into a : "All other traffic" transaction.

Can someone explain to me why that is ? What can I do to ensure all my beans are seen by AD ?


Thanks

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

I've spent some time investigating and found the "obvious" answer to my problem. There is a limit of 50 transactions.

This is surprising to me. Is it to limit data collected? Obviously, I will select a few services that are of more importance to me, but why is there such a limit? If a transaction IS used, shouldn't it be tracked?

Thanks in advance.

0 Karma

Arun_Dasetty
Super Champion

Hi Daniel,

Please find the response to your queries inline:

>>>>> Is it to limit data collected?

Answer: Yes, there is a default limit on the number of different business transactions monitored

>>>>  I will select a few services that are of more importance to me, but why is there such a limit?

Answer: This is to make sure both agent and controller is not overloaded and the default settings is to make sure there are limits imposed on BT limit which also affects number of metrics sent by agent, however user can always prioritize BT detection and can define custom business trasactions to make sure expected BTs are not falling under other traffic,

You can exclude BTs that you are not interested and can define custom rules to overcome the BT limit as we not recommened increasing the default BT limit until unless if there is no option.

>>>>>>>> If a transaction IS used, shouldn't it be tracked?

Answer: Yes we track the BTs executed under all other traffic BT , you can exclude the unwanted BTs from discovered BT list so that BTs under all other traffic will fall under discovered BT list once BT limit is in control.

image.png

image.png

You might find the following  doc links more helpful here;

- http://docs.appdynamics.com/display/PRO13S/Organizing+Traffic+as+Business+Transactions

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

Let us know if that answers your queries.

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...