Skip to main content
The /armor:status skill provides a quick overview of your data observability status across all monitored assets.

​
Usage

/armor:status
Or ask naturally:
  • “Is my data healthy?”
  • “What’s the status of my warehouse?”
  • “Any issues I should know about?”

​
What It Shows

  • Overall health status: Healthy, Warning, or Critical
  • Asset summary: Total monitored assets
  • Freshness issues: Tables that are stale
  • Schema changes: Unacknowledged drift
  • Recent alerts: Alerts triggered recently

​
Example Output

=== Data Health Summary ===

Overall Status: WARNING

Assets: 45 monitored
Freshness: 2 stale tables
Schema: 1 unacknowledged change
Alerts: 3 in last 24 hours

Issues Requiring Attention:
1. orders table is 6 hours stale
2. customers table is 2 hours stale
3. users.phone_number column added (pending review)

Recommended Actions:
- Check ETL pipeline for orders and customers
- Review schema change in users table

Alerts

Detailed alert information

Investigate

Root cause analysis

Coverage

Monitoring coverage gaps