sentry-otel-exporter-setup

Configure the OpenTelemetry Collector to export traces and logs to Sentry.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/achmf/KostaHub --skill sentry-otel-exporter-setup-achmf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry-otel-exporter-setup
Source: https://github.com/achmf/KostaHub/tree/main/.agents/skills/sentry-otel-exporter-setup
Command: npx skills add https://github.com/achmf/KostaHub --skill sentry-otel-exporter-setup-achmf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves the complexity of manually configuring the OpenTelemetry Collector to route traces and logs to Sentry, ensuring seamless observability across multiple services.

Core Features & Use Cases

  • Automated Configuration: Sets up the Sentry Exporter with support for multi-project routing and automatic project creation.
  • Trace Connectedness: Integrates OTLP with Sentry SDKs to link distributed traces to errors and logs.
  • Use Case: Use this when you need to centralize telemetry from various microservices into Sentry to gain full-stack visibility without manually managing complex collector pipelines.

Quick Start

Use the sentry-otel-exporter-setup skill to configure the OpenTelemetry collector and enable trace connectedness for my application.

Frequently Asked Questions about sentry-otel-exporter-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure the OpenTelemetry Collector to export traces to Sentry?

To configure the OpenTelemetry Collector to export traces to Sentry, you use a Sentry Exporter component to manage collector installation, pipeline configuration, and environment variable setup for multi-project telemetry routing.

What is trace connectedness and how does OTLP integrate with Sentry?

Trace connectedness links distributed traces to errors and logs. It integrates with Sentry by using the OTLPIntegration to connect OpenTelemetry Collector data with Sentry SDKs, ensuring full-stack visibility across multiple services without manual pipeline management.

Can I route telemetry from multiple microservices to different Sentry projects automatically?

Yes, you can route telemetry from multiple microservices to different Sentry projects automatically. The Sentry Exporter supports multi-project routing and automated Sentry project provisioning to centralize observability data across your services.

How do I set up environment variables for multi-project telemetry routing in OpenTelemetry?

Setting up environment variables for multi-project telemetry routing in OpenTelemetry involves configuring the Sentry Exporter within your collector pipeline. This manages automated project provisioning and ensures traces and logs route correctly to their respective Sentry projects.

Does the Sentry Exporter support automated Sentry project provisioning for new microservices?

Yes, the Sentry Exporter supports automated Sentry project provisioning. When configuring the OpenTelemetry Collector, this feature automatically creates and manages Sentry projects to handle telemetry routing for new or existing microservices.

Why should I use the OpenTelemetry Collector instead of native Sentry SDKs for telemetry?

Using the OpenTelemetry Collector instead of native Sentry SDKs centralizes telemetry routing from various microservices into Sentry. It provides full-stack visibility, manages multi-project routing, and ensures trace connectedness via OTLPIntegration without manual pipeline management.