AppD Archive

Business Transaction Autodiscovery

CommunityUser
Splunk Employee
Splunk Employee

When using the autodiscovery method for capturing business transactions, we currently throw nothing out which means we get stuck with one off start up calls that take up slots and don't go away.

We would like to age these transactions out but is there a threshold we can set too? For instance in our test environment we might not test for a month or more but don't want to lose meaningful BTs. If a BT hits a specified calls/min level, can it be exempted from aging out? Or, a minimum calls/min level is needed to qualify as a BT in the first place?

Overall, we are looking to spend less time managing the BT identification by hand so any hints along that path would be helpful.

Tags (1)
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Introduction to Splunk AI

How are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. Lucky for ...

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 ...

Maximizing the Value of Splunk ES 8.x

Splunk Enterprise Security (ES) continues to be a leader in the Gartner Magic Quadrant, reflecting its pivotal ...