Skip to content

Anomaly Actions Introduction

The Anomaly category groups the two actions used to clean up inactive anomalies. An anomaly counts as inactive when it has no updates or comments during a period you set.

  • Archive: moves the anomaly out of the active queue but keeps the record.
  • Delete: removes the anomaly permanently.

Both run as part of a flow, so anomalies are cleaned up automatically instead of one by one.

When to Use Archive vs Delete

Action Use when Keeps history?
Archive You want to clean up long-ignored anomalies but still keep them available for audits, compliance, or future reference.
Delete You're removing noise or temporary anomalies (test data, high-volume events) and don't need to keep any record.

Warning

Delete is permanent. Once an anomaly is removed, it cannot be recovered. If you might need the record later (audit, compliance, retrospectives), use Archive instead.

Both actions are configured the same way. You define an Inactivity Period (how long an anomaly stays untouched before it qualifies) and, when needed, add Filter Conditions by datastore, status, or tag to limit which anomalies are affected. The only thing that changes is the outcome: Archive keeps the record, Delete removes it.

Next Steps