sentry-monitoring

Investigate Sentry errors, issue statuses, project stats, and releases via API scripts.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill sentry-monitoring-erwinv2k-tkg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry-monitoring
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/incidentfox/sre-agent/.claude/skills/observability-sentry
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill sentry-monitoring-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, and includes scripts (resource) components.

What problem does it solve? Investigating application errors in Sentry manually requires switching between dashboards and clicking through issues. This Skill lets you query Sentry issues, error statistics, and releases directly from your AI workflow using command-line scripts. ## Core Features & Use Cases - Issue Investigation: List unresolved issues with Sentry search query syntax, then drill into individual issue details including event counts, affected users, and permalinks. - Issue Management: Update issue status to resolved, unresolved, ignored, or resolvedInNextRelease without leaving your workflow. - Project & Release Monitoring: List organization projects, retrieve project event statistics at configurable resolutions, and review recent releases with new error counts. - Use Case: When an error spike is reported, list unresolved issues for the affected project, inspect the top issue's details, check recent releases for a regression, and mark stale issues as resolved. ## Quick Start Ask the AI to list all unresolved error-level issues in your Sentry project and show details for the most frequent one.

Frequently Asked Questions about sentry-monitoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list unresolved Sentry issues from the command line?

Run list_issues.py with the --project flag and a --query like "is:unresolved level:error". The script calls the Sentry API and prints each issue's level, short ID, title, event count, and status, or outputs JSON with the --json flag.

How do I update a Sentry issue status programmatically?

Use update_issue_status.py with --issue-id and --status. Supported status values are resolved, unresolved, ignored, and resolvedInNextRelease, sent via a PUT request to the Sentry issues endpoint.

What Sentry search query syntax can I use to filter issues?

The scripts accept standard Sentry query syntax such as is:unresolved, level:error, first-release:1.2.0, firstSeen:-24h, and assigned:[email protected]. Terms can be combined in a single query string passed to the --query flag.

Do I need a Sentry auth token in my environment variables?

Not necessarily. In production, credentials are injected by a proxy layer via SENTRY_BASE_URL, so no token is visible. For direct testing mode, set SENTRY_AUTH_TOKEN and the client targets https://sentry.io/api/0.

Why does the Sentry script fail with an organization error?

The scripts require SENTRY_ORGANIZATION to be set, since all API paths are scoped to an organization slug. If it is missing, the client raises a RuntimeError; set the variable or configure it in your environment before running.