Skip to main content
The /armor:alerts skill lets you query, filter, and manage data observability alerts.

​
Usage

/armor:alerts
Or ask naturally:
  • “What alerts fired yesterday?”
  • “Show me critical alerts”
  • “What’s alerting on the orders table?”

​
Filters

You can filter alerts by:
  • Status: triggered, acknowledged, resolved
  • Severity: critical, warning, info
  • Asset: specific table or data source
  • Time range: today, yesterday, this week

​
Example Queries

​
Recent Alerts

You: What alerts fired in the last 24 hours?

Claude: Found 5 alerts in the last 24 hours:

1. [CRITICAL] Freshness SLA breach - orders
   Triggered: Today 8:15 AM
   Status: Unresolved

2. [WARNING] Schema change detected - users
   Triggered: Today 6:30 AM
   Status: Acknowledged

3. [WARNING] Null rate increase - products.category_id
   Triggered: Yesterday 11:00 PM
   Status: Resolved

4. [INFO] New table discovered - staging.temp_orders
   Triggered: Yesterday 9:00 PM
   Status: Acknowledged

5. [INFO] Freshness recovered - customers
   Triggered: Yesterday 4:00 PM
   Status: Auto-resolved

​
Filter by Severity

You: Show me only critical alerts

Claude: Found 1 critical alert:

[CRITICAL] Freshness SLA breach - orders
- Triggered: Today 8:15 AM
- Table: warehouse.public.orders
- SLA: 2 hours
- Current delay: 6 hours
- Status: Unresolved

This alert has been open for 4 hours.

​
Filter by Asset

You: What alerts are there for the customers table?

Claude: Found 2 alerts for customers:

1. [WARNING] Row count dropped 15% - customers
   Triggered: Yesterday
   Status: Investigating

2. [INFO] Schema change - customers.loyalty_tier added
   Triggered: Last week
   Status: Acknowledged

​
Managing Alerts

You can also manage alerts: 
You: Acknowledge the schema change alert

Claude: Acknowledged the schema change alert for users table.

Alert ID: alert-123
Status: acknowledged
Note: Schema change reviewed and approved

Status

Overall health check

Investigate

Dig into alert causes