By default, an active health rule violation displayed on the Health Rules Violations page is updated at 30- minute intervals after the initial violation event is triggered. AppDynamics first evaluates the health-rule condition against the configured critical or warning criteria. When the condition remains true for the configured evaluation and wait period, the Controller opens a health rule violation event.
While that violation remains active, AppDynamics periodically updates its displayed status and associated event information. The default continuation-update interval is 30 minutes. The violation is subsequently closed when the monitored metric no longer satisfies the violation criteria for the required duration.
The wait time after violation determines how long a condition must persist before AppDynamics opens the violation; it does not define the ongoing update frequency. The page is also not limited to updating only when a new violation starts, nor must an existing violation close before updated information can be recorded.
Relevant CAAPA Study Guide topics include Health Rule Evaluation, Warning and Critical Conditions, Wait Time After Violation, Health Rule Violation Events, Violation Lifecycle, and Controller Event Updates.

A transaction snapshot in AppDynamics is a detailed report of a single execution of a business transaction. Its primary purpose is to analyze issues with a specific business transaction by providing a comprehensive view of the transaction's execution path, including timing, call graphs, and database queries. This allows performance analystsand developers to drill down into individual transactions to diagnose performance bottlenecks, errors, or anomalies.
References:
AppDynamics documentation on Transaction Snapshots: Offers detailed guidance on how to capture and analyze transaction snapshots to troubleshoot and optimize application performance.

The Application Agent supports a default maximum of 50 Service Endpoints per entry point type. An entry point type represents the technology or execution mechanism through which the monitored request enters the application, such as a servlet, web service, message listener, or asynchronous processing framework.
This limit prevents excessive endpoint registration and metric creation at both the Agent and Controller layers. When Service Endpoint detection rules identify more endpoints than the configured threshold for a particular entry point type, the Agent restricts registration to the permitted maximum. The limit can be governed through the relevant Agent node-property configuration, but the standard tested value is 50.
The asynchronous-worker-thread options are too narrowly scoped and do not describe the general Service Endpoint registration limit. Likewise, 25 endpoints per entry point type is not the standard default Application Agent threshold.
This distinction is important because Service Endpoints generate independent performance metrics while remaining subordinate to the associated Business Transaction. Relevant CAAPA Study Guide topics include Service Endpoint Detection, Agent and Controller Limits, Entry Point Types, Agent Node Properties, Metric Registration, and Business Transaction Visibility.

When a Performance Analyst modifies an existing health rule that is already in a state of critical violation, the event that is typically triggered is "Health Rule Violation Continues - Critical." This event indicates that, despite the modification, the health rule is still being violated at a critical level. The system recognizes that the conditions for the health rule violation are still being met and continues to alert accordingly.
References:
AppDynamics documentation on Health Rules and Events: Explains the different types of health rule events and the conditions under which they are triggered.

To confirm if a memory leak is occurring, one should refer to the Tiers and Nodes section of the AppDynamics Controller UI, navigate to the Memory tab, and observe the Heap Utilization over time in relation to the Heap ' s Current Usage (MB) versus the Maximum (MB) allocated. Consistent growth in heap utilization or an upward trend that does not decrement even after garbage collection indicates a potential memory leak.
References: AppDynamics documentation on Memory Leak Detection and Heap Analysis.