The Performance Analyst should review Configuration > Instrumentation > Data Collectors. Business iQ commonly depends on transaction data collected from application code, including values obtained through method invocation data collectors. These collectors can be configured against specific class names, method names, method arguments, return values, object properties, or getter chains.

When developers refactor code and rename or relocate classes, an existing data collector may no longer match the instrumented method. As a result, the expected business data is not captured, and the related Business iQ fields, measures, or metrics can disappear from analytics views even though the application continues processing transactions.

The analyst should verify the configured class and method signatures, confirm that the new classes are instrumented, update any affected getter chains, and validate collection through new transaction snapshots or Analytics data.

The Errors page focuses on application exceptions, while Slow Transaction Thresholds controls performance classifications. Database collectors configure Database Visibility connections and are unrelated to application-code refactoring.

Relevant CAAPA Study Guide topics include Business iQ, Analytics Data Collection, Method Invocation Data Collectors, Class and Method Matching, Getter Chains, Instrumentation Configuration, and Transaction Snapshot Validation.