SolarWinds Observability-Self-Hosted-Fundamentals Exam - Topic 1 Question 3 Discussion

Alert escalation in the SolarWinds Platform allows for a tiered response to critical issues (e.g., emailing a technician immediately, then emailing a manager if the issue persists for 30 minutes). According to the SolarWinds HCO Alerting Engine documentation, the primary mechanism for a human operator to pause this automated progression is acknowledgement.

When an active alert is acknowledged via the Web Console, several things happen:

The alert is moved to the 'Acknowledged' category, signaling to other team members that the issue is being addressed.

The 'Acknowledge' timestamp and the user's name are recorded.

The escalation chain is halted. Any further actions defined in the 'Escalation' tab of the alert configuration---which were scheduled to fire after a certain duration---are cancelled.

It is important to note that acknowledging an alert does not clear the alert or stop the 'Reset Conditions' from being monitored. If the node stays down, the alert remains active, but no further new escalation emails will be sent. The alert will only truly disappear once the environment returns to a healthy state and the reset conditions are met.