In AppDynamics, how should the Transaction Detection rules be grouped logically?

An E-commerce application is built using microservices architecture design with several components.

In AppDynamics, how should the Transaction Detection rules be grouped logically?
A . Use Automatic Discovery
B . Use Scope
C . Use Transaction Group
D . Use Backend Detection

View Answer

Answer: C

Explanation:

For an e-commerce application built using a microservices architecture, logically grouping Transaction Detection rules can be effectively achieved through "Use Transaction Group." This approach allows for the organization of business transactions into meaningful groups that reflect the application’s structure and the interactions between its microservices. By grouping transactions, it becomes easier to monitor, analyze, and troubleshoot the application as a whole and its individual components, enhancing the visibility and management of the application’s performance.

Reference: AppDynamics documentation on Business Transactions: Provides insights on how to configure and manage business transactions, including grouping and monitoring strategies.

AppDynamics documentation on Microservices Monitoring: Offers guidance on best practices for monitoring applications designed with microservices architecture, including transaction grouping.