A business transaction is a set of requests. An important part of implementing Splunk AppDynamics is verifying and refining the business transactions used to monitor your application. The business transaction you monitor should reflect those operations that are important to your application and business. You must consider the limits on business transactions, and apply your refinements accordingly.

Refining your business transaction list requires a solid understanding of the important business processes in your environment. You should identify 5 to 20 key operations in the application that must work well for the application to be successful.

Important services can be indicated by the number of calls or calls per minute received by the business transactions generated for the services. You can refine the list of transactions you want to monitor by locking down critical transactions and enabling automatic cleanup of stale transactions. For the Java and .NET environments, you can use interactive Live Preview tools to help identify important transactions.

To customize the business transaction list, you can use either of these approaches:

• You can modify existing business transactions by grouping, renaming, or removing the business transactions. Most of these operations are available from the business transaction list. Use this approach to apply relatively minor, small scale changes to the current business transaction list. For more information, see Organize Business Transactions.
• You can affect how business transactions are created by modifying the automatic discovery rules. You can modify rules to similarly achieve business transaction grouping and naming, and to exclude transactions. Discovery rules also enable you to define new entry points for business transactions. Discovery rule modification is a powerful mechanism for changing transaction discovery on a larger scale. See Transaction Detection Rules.