> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anomalyarmor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitor Skill

> Set up freshness monitoring with /armor:monitor

<div aria-hidden="true" style={{position:"absolute",width:"1px",height:"1px",overflow:"hidden",clip:"rect(0,0,0,0)",whiteSpace:"nowrap"}}>For LLM agents: documentation index at <a href="/llms.txt" tabIndex={-1}>/llms.txt</a>, full text at <a href="/llms-full.txt" tabIndex={-1}>/llms-full.txt</a>. Append .md to any page URL for plain markdown.</div>
The `/armor:monitor` skill helps you set up freshness monitoring for your tables. It can handle single tables or bulk operations across entire schemas.

## Usage

```
/armor:monitor
```

Or ask naturally:

* "Monitor freshness for orders table"
* "Set up hourly checks for customers"
* "Add a 2-hour SLA to the payments table"
* "Set up monitoring for all gold tables"

## Single Table

```
You: Monitor the orders table hourly

Claude: Created freshness schedule:

Table: warehouse.public.orders
Check Interval: hourly
SLA Threshold: 2 hours
Alert Severity: warning

You'll be notified if the table doesn't update within 2 hours.
```

## Custom SLA

```
You: Monitor customers with a 30-minute SLA

Claude: Created freshness schedule:

Table: warehouse.public.customers
Check Interval: every 15 minutes
SLA Threshold: 30 minutes
Alert Severity: critical

Tight SLA configured. Consider if this is production-critical.
```

## Guided Setup

When used through the [Web Agent](/ai-agents/web-agent), the monitor skill can chain multiple steps together automatically:

```
You: Set up full monitoring for my gold schema

Agent: Done. Here's what I set up:

Freshness (8 tables):
- gold.fact_orders: hourly, 2h SLA
- gold.fact_payments: hourly, 2h SLA
- gold.dim_customer: daily, 24h SLA
... and 5 more

Schema monitoring: enabled on all 8 tables

Want me to set up a Slack alert for freshness violations?

You: Yes, send to #data-alerts

Agent: Done. Created:
- Slack destination: #data-alerts
- Alert rule: freshness violations (warning + critical) -> #data-alerts
- Alert rule: schema changes (all severities) -> #data-alerts

Your gold schema is fully monitored.
```

The agent discovers tables, creates schedules, enables schema monitoring, and wires up alerts, all in one conversation.

## Smart Recommendations

The agent can suggest monitoring intervals based on your table's update patterns:

```
You: What monitoring should I set up for the orders table?

Claude: Based on the orders table update history:
- Updates every ~45 minutes during business hours
- Recommended: 30-minute check interval, 90-minute SLA
- This balances alert noise with detection speed

Want me to create this schedule?
```

## Common Questions

### Can I set up monitoring for a whole schema at once?

Yes. Ask "monitor all tables in the gold schema" or "add freshness to every fact table." The skill expands the pattern, previews the tables, and creates schedules after you confirm.

### What freshness interval should I pick if I don't know my update cadence?

Don't guess. Use [`/armor:recommend`](/ai-agents/skills/recommend) to get an interval based on the table's historical update frequency, or [`/armor:test`](/ai-agents/skills/test) to dry-run a threshold against the last 30 days before enabling.

## Related Skills

<CardGroup cols={2}>
  <Card title="Status" icon="heart-pulse" href="/ai-agents/skills/status">
    Health check
  </Card>

  <Card title="Coverage" icon="chart-pie" href="/ai-agents/skills/coverage">
    Find gaps
  </Card>

  <Card title="Web Agent" icon="message-bot" href="/ai-agents/web-agent">
    In-app AI assistant
  </Card>

  <Card title="Quality" icon="shield-check" href="/ai-agents/skills/quality">
    Data quality metrics
  </Card>
</CardGroup>