A Scope is used to apply Transaction Detection Rules selectively to one or more tiers that perform the same or a related application function. Scoping allows a Performance Analyst to avoid applying a custom match rule or exclude rule across the entire application when the relevant entry point, framework, class, method, or request pattern exists only within particular tiers.
For example, several web-service tiers may use the same transaction naming convention or custom entry-point logic. The analyst can group those tiers within a scope and associate the transaction detection rule with that scope. This provides consistent detection behavior while preventing the rule from affecting unrelated application tiers.
Scopes are not primarily defined for individual nodes because nodes inherit transaction detection behavior from their tier-level configuration. They are also not used for backends, which are identified through exit-point and backend detection configuration. Transaction Detection Rule scopes remain within the context of a single monitored application and are not used to distribute one rule across multiple applications.
Relevant CAAPA Study Guide topics include Transaction Detection, Rule Scopes, Tier-Level Instrumentation, Custom Match Rules, Exclude Rules, Entry-Point Detection, and Application Agent Configuration.
