To streamline the monitoring process and enhance the relevance of collected data, AppDynamics allows Performance Analysts to exclude certain Java classes and methods from instrumentation. This is done through the " Configuration > Instrumentation > Call Graph Settings " menu, where irrelevant packages and classes can be specified for exclusion. This approach prevents the AppDynamics agent from tracking unnecessary or irrelevant methods, thus reducing overhead and focusing on the most critical aspects of application performance.
References:
AppDynamics documentation on Call Graph Settings: This section details how to configure call graph settings, including the exclusion of specific classes and methods from instrumentation, to optimize performance monitoring.

HTTP Request and Custom Actions are the two action types designed to integrate AppDynamics policy events with external alerting or event-management platforms.
An HTTP Request action sends an outbound request to a configured third-party endpoint when a policy is triggered. The analyst can specify the URL, HTTP method, authentication, headers, and event payload. This is commonly used with webhook-enabled alerting, incident-management, automation, and collaboration systems.
A Custom Action extends the Controller's standard action framework through a custom action module. It is appropriate when the external platform requires specialized processing, a proprietary protocol, payload transformation, or integration logic that cannot be handled by a standard HTTP request.
Notifications primarily deliver native email or SMS messages. Diagnostics initiate troubleshooting activities such as diagnostic sessions or thread dumps, while Remediation performs corrective operations. Issue Tracking System Integrations are specifically intended for creating or updating work items in supported issue- management platforms rather than providing a general alerting integration mechanism.
Relevant CAAPA topics include Health Rules, Policies, Policy Actions, HTTP Request Actions, Custom Actions, Webhook Integration, and Third-Party Event Management.

Business Transaction Discovery Sessions are supported for Java and .NET applications. These sessions help a Performance Analyst identify candidate transaction entry points when automatic discovery does not detect a proprietary framework, background process, scheduled task, or other nonstandard execution path.
During a discovery session, the Application Agent observes executed application code and allows the analyst to browse relevant classes and methods. The selected method can then be used to create or refine a Custom Match Rule, establishing a new Business Transaction entry point with appropriate naming and scope.
Java and .NET agents provide the runtime instrumentation and class-method visibility required for this workflow. C++, PHP, and Node.js applications have their own supported monitoring and transaction- detection capabilities, but they do not use the Business Transaction Discovery Session feature referenced in this question.
Discovery sessions should be run for a controlled period while representative application traffic exercises the target code path. The resulting class and method information can then be reviewed before creating a permanent transaction detection rule.
Relevant CAAPA Study Guide topics include Business Transaction Discovery Sessions, Java Agent, .NET Agent, Class and Method Browsing, Custom Match Rules, Entry-Point Detection, and Transaction Naming.

URI Segments should be used in Transaction Detection rules when the application is web-oriented. Web- oriented applications often have meaningful information in the URI that can identify different business transactions. URI Segments can help in defining patterns that match specific parts of the URI to distinguish different transactions.
References:
AppDynamics documentation on Transaction Detection: https://docs.appdynamics.com/latest/en/application- monitoring/business-transactions

When new business transactions are not appearing on the Business Transaction Dashboard after deploying new code, developers should verify that there are no exclusion rules in place on the tier where the new code was deployed. Additionally, it is crucial to ensure that the Auto Discovery feature for servlets is enabled for Java agents, as this allows AppDynamics to automatically detect and name business transactions based on incoming requests to servlets. Both of these checks are necessary to ensure that new business transactions can be discovered and monitored.
References: AppDynamics documentation on Business Transaction detection and Java Agent configuration.