In Hybrid Cloud Observability (HCO), specifically within theAlertStackfeature, related alerts are grouped into clusters to reduce "alert fatigue" and provide a unified view of an incident. According to theSolarWinds HCO Alerting Guide, an alert cluster transitions through several states based on the status of the underlying trigger conditions.
When the primary issues that triggered the alerts within the cluster are addressed and the "Reset Conditions" for those alerts are satisfied, the cluster is automatically managed by the system. The term used to define a cluster that has met its end conditions isauto-closed. Unlike manual "acknowledgment" or "resolution," which are user-driven actions, "auto-closed" signifies that the platform's monitoring engine has verified the environment has returned to a healthy state and the cluster no longer requires active monitoring or intervention. This automated lifecycle management is central to the AIOps and machine-learning capabilities of the platform, ensuring that the dashboard only reflects currently active, actionable incidents rather than historical events that have already been naturally corrected.