Use when configuring Sentry alerts, managing issues, or setting up notifications. Covers alert rules, issue triage, and integrations.
View on GitHubTheBushidoCollective/han
jutsu-sentry
January 24, 2026
Select agents to install to:
npx add-skill https://github.com/TheBushidoCollective/han/blob/main/jutsu/jutsu-sentry/skills/alerts-issues/SKILL.md -a claude-code --skill sentry-alerts-issuesInstallation paths:
.claude/skills/sentry-alerts-issues/# 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 1. **Unresolved**: Active issue needing attention 2. **Resolved**: Fixed in a release 3. **Ignored**: Intentionally dismissed 4. **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: 1. Select issues to merge 2. Choose primary issue 3. All events appear under primary ### Ignore Rules ``` Ignore this issue: - Forever - Until it happens again - For the next 24 hours - Until it affects
Issues Found: