Integration / Apache Pulsar Interview questions
What is a Data Collector in AppDynamics?
A Data Collector captures extra context alongside a transaction snapshot — an HTTP header value, a request parameter, a piece of business data passed as a method argument, or a JMX attribute — so that when you're looking at a slow or errored snapshot, you can see not just the timing but relevant business context too, like a customer ID or order type.
Configuring one means specifying where the data lives (HTTP header/parameter, POJO method parameter, or JMX) and whether it should also be usable for filtering and custom match rules, not just for display in the snapshot viewer.
This is especially useful for correlating performance problems with business segments — for example, discovering that slow checkouts disproportionately involve a specific promo code parameter, which points investigation toward a specific discount-calculation code path rather than the checkout flow in general.
More Related questions...
