Sentry Ecosystem

Sentry is the error tracking and release-health route when the work is about exceptions, issue triage, source maps, releases, alerts, performance traces, or SDK instrumentation. Source: Ecosystem Capability Coverage, 2026-06-27; Skill Resolver, 2026-06-27

When To Use This

Use Sentry when user-visible failures need issue grouping, stack traces, release association, source maps, or alerting. Use general observability pages for telemetry strategy, but route implementation and triage through Sentry-specific tools when Sentry is named. Source: Skill Resolver, 2026-06-27

Decision Matrix

Core Model

Sentry connects runtime errors to release context. It is not a generic logs warehouse. It should answer "what user-facing failure happened, in which release, and what code path produced it?" Source: Observability Architecture, 2026-06-27

Routing Summary

Preferred order: Sentry MCP for issue and alert reads, plugin skills for setup/workflow/code review, then sentry-cli for releases, source maps, debug files, and issue metadata. Source: Skill Resolver, 2026-06-27; config/capability-harvest-seeds.json

Failure Modes

• Instrumenting without release/source-map linkage.
• Treating logs as a substitute for grouped exceptions.
• Sending noisy alerts without ownership or runbook.
• Fixing an issue without proving the release path changed.

Verification Path

Run sentry-cli info or a read-only MCP lookup to confirm org/project. For instrumentation, send a test event and verify project, environment, release, and source-map resolution. Source: config/capability-harvest-seeds.json; Skill Resolver, 2026-06-27

---

Timeline

• 2026-06-27 | Canonical ecosystem page created to promote Sentry from registry evidence into observability routing and pack placement. Source: User request, 2026-06-27; Ecosystem Capability Coverage