sentry-skill_skill

Overview

This skill provides a comprehensive toolkit for configuring and automating Sentry error monitoring, performance tracking, and observability workflows. It covers SDK setup across languages, release and source map management, API-driven queries, alerting rules, sampling strategies, and self-hosted deployments. Use it to standardize Sentry operations and embed observability into CI/CD and runtime environments.

How this skill works

The skill supplies concrete configuration patterns for Sentry SDKs (JavaScript/Node, Python, Go) including error capture, breadcrumbs, scopes, transactions, and distributed tracing. It documents Sentry CLI and API workflows for creating releases, uploading source maps and debug symbols, querying issues and events, and managing alerts. It also outlines self-hosted install steps, system requirements, and integrations with OpenTelemetry for OTLP ingestion.

When to use it

• Configure Sentry SDKs and integrate performance tracing into services.
• Automate release creation, source map uploads, and deploy tagging in CI/CD.
• Query or manage issues, events, and releases via the Sentry API or CLI.
• Set up alerting, notification channels, and metric-based triggers.
• Deploy or scale a self-hosted Sentry instance and connect external storage.
• Integrate OpenTelemetry to unify traces across distributed services.

Best practices

• Use dynamic traces sampling to reduce noise while always sampling error cases.
• Scrub PII and sensitive headers in beforeSend hooks before sending events.
• Annotate releases and upload source maps/debug symbols to enhance stack traces.
• Use isolated scopes for per-request context and set user/tags for grouping.
• Respect API rate limits; paginate requests and use Link headers to iterate.
• For self-hosted, provision recommended CPU/RAM/disk and external object storage.

Example use cases

• CI job that creates a release, associates commits, uploads source maps, and finalizes the release via sentry-cli.
• Instrumenting a Node service to start transactions, create child spans, and propagate sentry-trace across HTTP calls for distributed tracing.
• A cron wrapper that reports monitor check-ins using sentry-cli to alert on missed jobs.
• Automated script that queries unresolved issues in the last 24 hours and posts a summary to Slack.
• Deploying a self-hosted Sentry cluster with external PostgreSQL, Redis, and S3-compatible filestore, then scaling worker services.