Skip to main content
The /armor:test skill lets you dry-run monitoring configurations before enabling them. Preview what alerts would fire to avoid alert fatigue.

​
Usage

/armor:test
Or ask naturally:
  • “Test this freshness threshold before I enable it”
  • “What alerts would fire with a 4-hour threshold?”
  • “Dry-run the schema drift check”
  • “Preview the impact of this alert rule”
  • “Will this configuration cause too many alerts?”

​
What It Does

​
Freshness Dry-Run

Preview what would happen with a proposed freshness threshold:
  • Compares the threshold against historical update patterns
  • Shows how many times the table would have been flagged as stale
  • Helps you pick a threshold that catches real issues without false positives

​
Schema Drift Preview

Test schema monitoring before enabling:
  • Compares current schema against a baseline
  • Shows what changes would be detected
  • Estimates alert frequency based on historical schema change rate

​
Alert Rule Preview

Preview which alerts would fire with proposed rule settings:
  • Test event type filters and severity levels
  • See which recent events would match the rule
  • Estimate daily alert volume

​
Example

You: Test a 4-hour freshness threshold on gold.orders

Agent: I'll dry-run that threshold against recent data.

Dry-run results for gold.orders with 4h threshold:
  - Last 30 days: 3 stale events would have fired
  - Average gap between updates: 55 minutes
  - Longest gap: 3h 42m (March 15, during maintenance)
  - Recommendation: 4h is a good threshold. It catches real
    staleness without firing during normal variation.

Want me to enable this? I'll use /armor:monitor to set it up.
  • Recommend - Get suggestions for what to monitor
  • Monitor - Enable monitoring after testing
  • Quality - Set up data quality checks