sentry-otel-exporter-setup

sentry-otel-exporter-setup is a skill for Claude Code, Codex from getsentry/plugin-claude. It costs 57 tokens per session (4,321 once invoked), scanned A, a copy of sentry-otel-exporter-setup, MIT.

A procedure for configuring the OpenTelemetry Collector, a service that receives and forwards application measurements, to send traces and logs to Sentry through the Sentry Exporter.

In plain words
What is it for?
Use it when connecting OpenTelemetry traces and logs to Sentry, configuring several services or projects, and verifying the resulting collector setup.
Why use it?
It guides the setup of multi-project telemetry routing and automatic Sentry project creation while checking the existing configuration first.

Skill for Claude CodeCodex

Part of the sentry plugin — 8 skills shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/getsentry/plugin-claude/sentry-otel-exporter-setup
Any agent
npx skills add getsentry/plugin-claude --skill sentry-otel-exporter-setup
Clone the repo
git clone --depth 1 https://github.com/getsentry/plugin-claude

Made for: Claude Code, Codex.

Or install sentry, the plugin that ships this one along with the rest of its 8 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sentry-otel-exporter-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/getsentry/plugin-claude/sentry-otel-exporter-setup.svg)](https://agentmods.dev/skills/getsentry/plugin-claude/sentry-otel-exporter-setup)
Your own site
<a href="https://agentmods.dev/skills/getsentry/plugin-claude/sentry-otel-exporter-setup"><img src="https://agentmods.dev/badge/skills/getsentry/plugin-claude/sentry-otel-exporter-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,321 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00057 $0.04321
Opus 5 $0.00028 $0.02160
Sonnet 5 $0.00011 $0.00864
Haiku 4.5 $0.00006 $0.00432

Measured 4d ago against content hash 8671e32a5d05, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sentry-otel-exporter-setup scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s https://api.github.com/repos/open-telemetry/opentelemetry-collector-releases/releases/latest | grep '"tag_name"' | cut -d'"' -f4
Origin

This is a copy

100% identical to sentry-otel-exporter-setup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/sentry-otel-exporter-setup/SKILL.md · 485 lines

How it starts

The opening of the file, as written. The whole thing — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 8: Enable trace connectedness with OTLPIntegration (Python/Ruby/Node.js)

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

Wait for the user’s answer and record their choice before proceeding to Step 2. The rest of the workflow depends on this decision.

If no config exists: Note that you’ll create a new collector-config.yaml in Step 4, then proceed to Step 2.

Step 2: Check Collector Version

The Sentry Exporter requires otelcol-contrib v0.145.0 or later.

Check for existing collector

  1. Run which otelcol-contrib to check if it’s on PATH, or check for ./otelcol-contrib in the project
  2. If found, run the appropriate version command and parse the version number
  3. Record the collector path (e.g., otelcol-contrib if on PATH, or ./otelcol-contrib if local) for use in later steps
Existing Version Action
≥ 0.145.0 Skip to Step 3 — existing collector is compatible
< 0.145.0 Proceed with installation below
Not installed Proceed with installation below

Read the full file on GitHub · 485 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 485 lines · 57 tokens per session scan A 8671e32a5d05

Subscribe to this mod's changes

sentry-otel-exporter-setup is a skill published in the GitHub repository getsentry/plugin-claude (4 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 4,321 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to sentry-otel-exporter-setup, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens