Skip to main content
The /armor:coverage skill analyzes what’s being monitored and identifies gaps in your data observability coverage.

Usage

Or ask naturally:
  • “What am I monitoring?”
  • “What tables have no alerts?”
  • “Show me monitoring gaps”
  • “Which tables need freshness checks?”

Coverage Categories

  • Freshness: Tables with/without freshness schedules
  • Schema: Tables with/without schema baselines
  • Metrics: Tables with/without data quality metrics
  • Alerts: Tables with/without alert rules

Example Usage

Coverage Overview

Find Unmonitored Tables

Prioritize Gaps

Common Questions

What counts as a ‘good’ coverage score?

Production tables should be at 100%. Staging in the 70-90% range is typical. Raw/landing and archive tables often don’t need full coverage, so anything above 50% there is usually fine. The overall letter grade weights production tables most heavily.

How do I exclude sandbox or archive tables from my coverage score?

Tag them with a governance tag (like sandbox or archive) using /armor:tags. The coverage skill respects exclusion tags so your score reflects only the tables you actually care about.

Monitor

Set up monitoring

Quality

Add quality checks

Status

Health overview