After you determine a set of business transactions to monitor, you may want to lock down business transactions. Locking down business transactions prevents application changes, upgrades to the agent software, or other changes from affecting the number or selection of business transactions you monitor as the primary, first-class business transactions in the Splunk AppDynamics model of your environment.

A production implementation of Splunk AppDynamics involves an initial period of assessing, organizing, and refining business transactions by customizing your default business transaction discovery rules.

With business transaction lockdown enabled, the Controller moves newly discovered transactions under the Overflow tab. You can promote a business transaction from the Overflow list by registering it as a first-class business transaction manually.

Business transaction lockdown provides a way to register business transactions individually, by manual selection. In certain scenarios, you may want to enable business transaction lockdown before discovery occurs and register transactions manually. For example, this may be useful if your environment would otherwise generate a large number of business transactions and you only want to monitor a relative few as first class business transactions.