After reviewing a problem that caused an outage, a Performance Analyst wants to create a...

AppDynamics health-rule criteria provide two supported methods for evaluating multiple conditions: All of the following conditions are met and Any of the following conditions are met.

Selecting All applies logical AND behavior. Every configured condition must evaluate as true during the health rule’s evaluation period before AppDynamics generates the warning or critical violation. For the outage scenario, this is the appropriate selection when the alert must occur only when several symptoms—such as elevated response time, increased errors, and high CPU utilization—happen together.

Selecting Any applies logical OR behavior. AppDynamics creates the violation when at least one configured condition becomes true. This is useful when several independent symptoms can indicate the same operational problem.

Although “And” and “Or” describe the underlying logical concepts, they are not the named values presented for multi-condition health-rule evaluation in this context. The interface uses All and Any.

Relevant CAAPA Study Guide topics include Health Rule Conditions, Warning and Critical Criteria, Condition Evaluation Logic, Evaluation Time, Violation Wait Time, and Policy Triggering.