sentry
/sentry
Set up and operate Sentry for error tracking, performance monitoring, and release health. Use for SDK integration, alert tuning, and incident investigation.
- Author
- v1truv1us ↗
- Repository
- ai-eng-system ↗
- Licence
- MIT
- Last repository change
- 09.08.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 5
No signals detected. Repository changed on 09.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Set up and operate Sentry for error tracking, performance monitoring, and release health. Use for SDK integration, alert tuning, and incident investigation.
Original author description
Set up and operate Sentry for error tracking, performance monitoring, and release health. Use for SDK integration, alert tuning, and incident investigation.
How it works
- Current Versions (Verify Before Use)
- Core Principles
- SDK Integration Checklist
- Alert Configuration
- Performance Monitoring
- Common Anti-Patterns
- Troubleshooting Flow
- Official Resources
SKILL.md preview
---
name: sentry
description: Set up and operate Sentry for error tracking, performance monitoring, and release health. Use for SDK integration, alert tuning, and incident investigation.
metadata:
category: user-invoked
disable-model-invocation: true
---
Default output: return only the result, blockers, and required evidence. Omit preambles, process narration, repeated context, confidence scores, and follow-up offers. Use at most five bullets unless a required artifact or schema needs more.
# Sentry Operations
## Current Versions (Verify Before Use)
Check the [Sentry SDK releases](https://github.com/getsentry/sentry-javascript/releases) for your platform. SDKs follow semver independently.
## Core Principles
1. **Instrument before you need it.** Sentry is most valuable when it's already running before an incident.
2. **Alert on new issues, not total volume.** A spike in errors you've already seen is less actionable than a new error type.
3. **Breadcrumbs tell the story.** Good instrumentation includes HTTP requests, state transitions, and user actions leading to the error.
4. **Performance is part of observability.** Enable distributed tracing to connect frontend errors to backend root causes.
## SDK Integration Checklist
### Error Tracking
- [ ] DSN configured via environment variable (not hardcoded)
- [ ] `release` set to git SHA or version tag
- [ ] `environment` set (production, staging, development)
- [ ] Global error handler captures unhandled exceptions
- [ ] Rejected promises are captured (frontend + backend)
- [ ] Source maps uploaded for JS/TS (enables readable stack traces)
### Performance
- [ ] Tracing enabled with appropriate sample rate
- [ ] Custom spans for critical operations (DB queries, external API calls)
- [ ] Distributed tracing headers propagated between services
- [ ] Database queries auto-instrumented or manually spanned
### Context
- [ ] User ID attached (hashed, not PII)
- [ ] Tags for team/service/component
- [ ] Breadcrumbs for state changes
## Alert Configuration
```javascript
// Example: Alert on new issues in production
// Sentry UI → Alerts → Create Alert Rule
// When: A new issue is created
// If: Environment equals "production"
// Then: Send notification to Slack #alerts
```
**Alert hierarchy:**
1. **New issue in production** → Immediate notification
2. **Issue count > 100/hour** → Page on-call (regression)
3. **Performance regression > 20%** → Slack notification
4. **Release crash rate > 1%** → Block deployment
## Performance Monitoring
### Key Metrics
- **Apdex:** User satisfaction score (0-1)
- **P50/P95/P99 Latency:** Response time distribution
- **Throughput:** Requests per minute
- **Failure Rate:** Error % of total requests
### Custom Spans
```javascript
const span = Sentry.startSpan({ name: 'process-payment' }, () => {
// critical operation
});
```
## Common Anti-Patterns
| Anti-Pattern | Why It's Wrong | Fix |
|---|---|---|
| Hardcoded DSN | Secret exposure, can't rotate per env | Environment variable |
| No source maps | Stack traces are minified gibberish | Upload maps in CI |
| 100% trace sampling | Expensive, unnecessary | 1-10% for high traffic |
| No release association | Can't correlate errors with deployments | Set `release` to git SHA |
| Ignoring caught errors | Silent failures accumulate | Log or capture explicitly |
| PII in context | Privacy violations | Hash IDs, strip emails/phones |
## Troubleshooting Flow
1. **New error spike:** Check release timing → correlate with deployment
2. **Minified stack trace:** Source maps not uploaded or mismatch
3. **Missing errors:** Check filters, sampling rate, DSN correctness
4. **Performance blind spot:** Check trace propagation between services
5. **Alert fatigue:** Review alert rules, add thresholds, use issue states
## Official Resources
- [Sentry docs](https://docs.sentry.io/)
- [JavaScript SDK](https://docs.sentry.io/platforms/javascript/)
- [Performance monitoring](https://docs.sentry.io/product/performance/)
- [Source maps](https://docs.sentry.io/platforms/javascript/sourcemaps/)
Files in this package (2)
- SKILL.md 4 KB
- evals/evals.json 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · v1truv1us/ai-eng-system | 100 | MIT |
| sgtlaugh/skills | 100 | MIT |
| cardstack/boxel | 100 | MIT |
| znlgis/opengis-skills | 100 | MIT |
| TerminalSkills/skills | 100 | Apache-2.0 |
| tech-leads-club/agent-skills | 100 | MIT |
| foryourhealth111-pixel/Vibe-Skills | 100 | Apache-2.0 |
| getsentry/junior | 100 | Apache-2.0 |
| greedychipmunk/agent-skills | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 200f6fe1bb80 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100sentry-performance-tuning
Optimize Sentry performance monitoring configuration. Use when tuning sample rates, reducing overhead, or improving performance data quality. Trigger with phrases like "sentry performance optimize", "tune sentry tracing", "sentry overhead", "improve sentry performance". - 100sentry-performance-tracing
Set up performance monitoring and distributed tracing with Sentry. Use when implementing performance tracking, tracing requests, or monitoring application performance. Trigger with phrases like "sentry performance", "sentry tracing", "sentry APM", "monitor performance sentry". - 100sentry-deploy-integration
Track deployments and releases in Sentry. Use when configuring deployment tracking, release health, or connecting deployments to error data. Trigger with phrases like "sentry deploy tracking", "sentry release health", "track deployments sentry", "sentry deployment notification". - 100sentry-sdk-setup
Set up Sentry in any language or framework. Detects the user's platform and loads the right SDK skill. Use when asked to add Sentry, install an SDK, or set up error monitoring in a project. - 100sentry-release-management
Manage Sentry releases with versioning, commit association, and source map uploads. Use when creating releases, linking commits to errors, uploading release artifacts, monitoring release health, or cleaning up old releases. Trigger with phrases like "sentry release", "create… - 100mcp-server-sentry
Use this skill when installing, configuring, and executing tools with the Sentry error tracking, stack traces, and issue triage Sentry MCP server.