[betegon]

alert metrics view drops thresholds and linked notification workflows, so it cannot answer when an alert fires or whom it notifies. Preserve the detector settings and inspect linked workflows, including their filters, destinations, and enabled states. JSON keeps the existing fields and adds native configuration and workflow documents, with --fields support.

Before

sentry alert metrics view test-org/9 shows an active alert, but omits its thresholds and notification configuration:

Name:         P95 latency
Status:       active
Dataset:      spans
Aggregate:    p95(span.duration)
Query:        environment:prod
Time Window:  5m

After

The same sanitized alert now exposes its thresholds and recovery condition, plus the disabled workflow containing its Slack action. Output excerpts:

│ Condition 1 │ >= 500 → high (75)                             │
│ Condition 2 │ <= 300 → OK / recovery (0)                     │

Workflow 12: Notify on-call
━━━━━━━━━━━━━━━━━━━━━━━━━━━

╭─────────────┬──────────────────╮
│ Status      │ disabled         │
│ Environment │ prod             │
│ Config      │ {"frequency":30} │
╰─────────────┴──────────────────╯

Action 1

│ Provider       │ slack                                                       │
│ Target         │ #backend_alerts                                             │
│ Status         │ active                                                      │

Works by ID or name. Missing or inaccessible workflows appear in workflowErrors (403/404); authentication, network, and server failures still propagate. This inspects current configuration, not notification delivery history.

Validated with 60 alert command/API/formatter tests, CLI typecheck, and lint/format for the changed files.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Oct 26, 2026 2:39pm UTC