sentry

Sentry error tracking and performance monitoring. Use for error tracking.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

sentry is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sentry error tracking and performance monitoring. Use for error tracking.

Teams using sentry should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/sentry/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/devops/sentry/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/sentry/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How sentry Compares

Feature / Agent	sentry	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Sentry error tracking and performance monitoring. Use for error tracking.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Sentry

Sentry provides self-hosted and cloud-based error monitoring. In 2025, it excels at **Performance Monitoring** and identifying **AI Model** hallucinations or errors.

## When to Use

- **Error Tracking**: "My app crashed, what is the stack trace?"
- **Frontend Performance**: Web Vitals monitoring (LCP, FID).
- **Release Tracking**: Associate errors with specific git commits/releases.

## Quick Start

```javascript
import * as Sentry from "@sentry/node";

Sentry.init({
  dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
  tracesSampleRate: 1.0,
});

try {
  myFunction();
} catch (e) {
  Sentry.captureException(e);
}
```

## Core Concepts

### Issues

Aggregated groups of events. Sentry expects 1000 events of "NullPointerException" to be grouped into 1 Issue.

### Releases

Tying code versions to errors. Sentry can tell you "This error started in Release v3.4".

### Distributed Tracing

Connects frontend errors to backend bottlenecks.

## Best Practices (2025)

**Do**:

- **Upload Source Maps**: Essential for JS/TS debugging.
- **Use `ignoreErrors`**: Filter out noise (like "Network Error" when user is offline) in the SDK config.
- **Use Session Replay**: Video-like reproduction of user actions leading up to an error.

**Don't**:

- **Don't log PII**: Sanitize data before sending. Sentry has scrubbers, but do it client-side too.

## References

- [Sentry Documentation](https://docs.sentry.io/)