Which feature halts the alert escalation process?

In the SolarWinds Platform alerting engine, acknowledging an alert is a manual action taken by a user to indicate they are aware of the issue. This action takes ownership of the alert and, critically, halts the escalation process. This prevents subsequent notification tiers or more severe actions defined in the alert's configuration from being executed, allowing the user time to investigate and resolve the underlying problem without generating further unnecessary notifications.

B. Reset actions are executed only when the alert's reset conditions are met, signifying the issue is resolved, not just halted.

C. Reset conditions define the criteria for an alert to return to a normal state; they do not stop an active escalation.

D. Trigger actions are the initial set of operations that occur when an alert is first activated; they start the process, not halt it.

SolarWinds Platform Documentation, "Acknowledge alerts". (solarwinds.com/documentation/orion/docs/orionplatformcoreagacknowledgedalerts.htm). This document states, "When you acknowledge an alert, you are taking ownership of the triggered alert. Acknowledging an alert can stop the escalation of the alert, so that no further alert actions are executed."