DevOps / AppDynamics Interview questions
What is the difference between automatic and custom Business Transaction match rules?
Both approaches decide how incoming requests get grouped into named Business Transactions, but they trade off setup effort against precision.
| Automatic Discovery | Custom Match Rules |
| Built in, requires no configuration to start. | Explicitly authored by a team member. |
| Can over-generate BTs on high-cardinality URLs. | Can normalize a URL pattern, e.g. group /orders/* as one BT. |
| Applies generic framework-level detection logic. | Can match on URI, HTTP parameter, header, or custom logic. |
| Good for a first-pass, general view of traffic. | Good for isolating a specific business-critical flow precisely. |
A common pattern is to start with automatic discovery, watch the BT list for a few days, then add targeted custom rules only where discovery produced noisy or overly-granular results.
What can a custom match rule do that automatic discovery typically can't handle well?
What is a common practical workflow for using both approaches?
More Related questions...
