Splunk AppDynamics

Separate Business Transactions?

CommunityUser
Splunk Employee
Splunk Employee

Hallo,

so I checked the Business Transactions of my app and I noticed that the same BT has very good performance and then suddenly a very bad performance.. now I checked and the reason is that I do have some normal http queries and some have a db call where the app saves something to a DB, so obviously this takes much more time, so this should NOT count as the same BT, so what I want to do is to treat them as different BTs.

How can I do that?

I tried https://docs.appdynamics.com/display/PRO42/Custom+Naming+for+Servlet+Transactions#CustomNamingforSer...

but this did not help. Can someone help me please? Thank you!

Labels (3)
0 Karma

Jeanie_Kedia1
Communicator

@Anonymous let us know what you find and how it goes for you. 

0 Karma

Tobias_Rupprech
Engager

Hi norrington80,

the only way to differentiate would be to have different entry points for the BT(s). You did not describe any specifics to your use case, so the answer is a bit generic here.
If the two Calls to the application have different parameters or methods (the first one is a GET, the one with the DB Call is a POST), you could differentiate based on that.

I'm assuming you're dealing with a Java App, so you can try to set up a Custom Match Rule, like stated in the documentation:

https://docs.appdynamics.com/display/PRO42/Servlet+Entry+Points#ServletEntryPoints-CustomMatchRulesf...

Hope that helps,
Tobias

Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...