Claude-skill-registry sentry-alerts-issues

Use when configuring Sentry alerts, managing issues, or setting up notifications. Covers alert rules, issue triage, and integrations.

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/alerts-issues" ~/.claude/skills/majiayu000-claude-skill-registry-sentry-alerts-issues && rm -rf "$T"

manifest: skills/data/alerts-issues/SKILL.md

Sentry - Alerts & Issue Management

Configure alerts, manage issues, and set up notifications.

Alert Types

Issue Alerts

Trigger when an issue matches specific conditions:

New issue created
Issue changes state (resolved → unresolved)
Issue frequency exceeds threshold
Issue affects specific users/releases

Metric Alerts

Trigger based on aggregate metrics:

Error count exceeds threshold
Transaction latency (p50, p95, p99)
Failure rate percentage
Apdex score drops

Uptime Monitoring

Monitor endpoint availability:

HTTP status codes
Response time thresholds
SSL certificate expiration

Alert Conditions

Frequency-Based

When an issue is seen more than 100 times in 1 hour

User Impact

When an issue affects more than 50 unique users in 1 hour

First Seen

When a new issue is created

Regression

When an issue changes state from resolved to unresolved

Alert Actions

Notification Channels

Email: Individual or team distribution
Slack: Channel or direct messages
PagerDuty: On-call escalation
Discord: Webhook notifications
Microsoft Teams: Channel posts
Webhooks: Custom integrations

Issue Actions

Assign to team member
Add tags
Create ticket (Jira, Linear, GitHub)

Issue States

Lifecycle

Unresolved: Active issue needing attention
Resolved: Fixed in a release
Ignored: Intentionally dismissed
Archived: Historical, no longer tracked

Substates

For Review: Needs triage
Escalating: Increasing in frequency
Regressed: Previously resolved, now recurring
New: First seen recently

Issue Management

Merge Issues

Combine duplicate issues with different stack traces:

Select issues to merge
Choose primary issue
All events appear under primary

Ignore Rules

Ignore this issue:
- Forever
- Until it happens again
- For the next 24 hours
- Until it affects 100 users

Ownership Rules

# Define in project settings
path:src/payments/* #payments-team
path:src/auth/* user@example.com
tags.component:checkout #checkout-team

API Integration

List Issues

curl "https://sentry.io/api/0/projects/{org}/{project}/issues/" \
  -H "Authorization: Bearer $SENTRY_AUTH_TOKEN"

Update Issue

curl -X PUT "https://sentry.io/api/0/issues/{issue_id}/" \
  -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"status": "resolved"}'

Create Alert Rule

curl -X POST "https://sentry.io/api/0/projects/{org}/{project}/rules/" \
  -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "High Error Rate",
    "conditions": [...],
    "actions": [...],
    "frequency": 30
  }'

Integration Examples

Slack Alert

{
  "action": "notify_slack",
  "workspace": "your-workspace",
  "channel": "#alerts",
  "tags": ["level", "environment"]
}

PagerDuty Escalation

{
  "action": "notify_pagerduty",
  "service": "your-service-key",
  "severity": "critical"
}

Jira Ticket Creation

{
  "action": "create_jira_ticket",
  "integration": "jira-integration-id",
  "project": "PROJ",
  "issueType": "Bug"
}

Best Practices

Start with conservative thresholds, tune over time
Use different channels for different severities
Set up on-call rotation for critical alerts
Review and archive stale issues regularly
Define ownership rules for automatic assignment
Create runbooks for common alert types
Use metric alerts for SLO monitoring