Sentry Otel Exporter Setup

Sets up the OpenTelemetry Collector with Sentry's exporter to route traces and logs into Sentry projects. Walks through version checking (needs otelcol-contrib 0.145.0+), handles both binary and Docker installations, and generates or modifies collector configs with proper pipeline setup. The automatic project creation feature is handy for multi-service architectures but comes with a quirk: it assigns everything to your first team and may drop initial data during creation. Good attention to detail on environment variable handling, making it clear these are placeholders you fill in yourself. The checklist format and existing config detection save you from configuration conflicts when adding Sentry to an established observability stack.

skills.sh installs: 304
GitHub stars: 25
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add getsentry/sentry-agent-skills --skill sentry-otel-exporter-setup --agent claude-code

Installs into .claude/skills of the current project.

Files

Sentry OTel Exporter Setup

Terminology: Always capitalize "Sentry Exporter" when referring to the exporter component.

Configure the OpenTelemetry Collector to send traces and logs to Sentry using the Sentry Exporter.

Setup Overview

Copy this checklist to track your progress:

OTel Exporter Setup:
- [ ] Step 1: Check for existing configuration
- [ ] Step 2: Check collector version and install if needed
- [ ] Step 3: Configure project creation settings
- [ ] Step 4: Write collector config
- [ ] Step 5: Add environment variable placeholders
- [ ] Step 6: Run the collector
- [ ] Step 7: Verify setup

Step 1: Check for Existing Configuration

Search for existing OpenTelemetry Collector configs by looking for YAML files containing receivers:. Also check for files named otel-collector-config.*, collector-config.*, or otelcol.*.

If an existing config is found: Ask the user which approach they want:

Modify existing config: Add Sentry Exporter to the existing file (recommended to avoid duplicates)
Create separate config: Keep existing config unchanged and create a new one for testing

SKILL.md on GitHub