autotel-sentry

Map OpenTelemetry spans to Sentry transactions for Node.js observability.

7|3|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/jagreehal/autotel --skill autotel-sentry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autotel-sentry
Source: https://github.com/jagreehal/autotel/tree/main/packages/autotel-sentry/skills/autotel-sentry
Command: npx skills add https://github.com/jagreehal/autotel --skill autotel-sentry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables seamless integration of OpenTelemetry traces with Sentry, bridging performance monitoring and error tracking for comprehensive observability.

Core Features & Use Cases

  • Trace bridging: Converts OTel spans into Sentry transactions and spans to synchronize performance data.
  • Distributed tracing propagation: Injects and extracts sentry-trace and baggage headers for cross-service trace stitching.
  • Use Case: When deploying a Node.js application using autotel and Sentry, this Skill ensures that traces and errors are linked in both systems, simplifying debugging and analysis.

Quick Start

Initialize Sentry before autotel and register the span processor to enable trace conversion and error linking during your application runtime.

Frequently Asked Questions about autotel-sentry

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

FAQPage Schema
How do I integrate OpenTelemetry spans with Sentry for unified performance monitoring?

To integrate OpenTelemetry spans with Sentry, initialize Sentry before autotel and register the span processor to convert OTel spans into Sentry transactions, synchronizing performance data and error tracking.

Can I stitch distributed traces across Node.js services using sentry-trace and baggage headers?

Yes, distributed tracing propagation injects and extracts sentry-trace and baggage headers to enable cross-service trace stitching, ensuring trace consistency across Node.js applications using OpenTelemetry and Sentry.

What is the best way to link OpenTelemetry traces to Sentry errors in a Node.js app?

The best way to link traces to errors is mapping OpenTelemetry spans to Sentry transactions, which enriches error context and bridges performance monitoring data with Sentry's error tracking during runtime.

Does this OpenTelemetry to Sentry trace bridging work without additional dependencies?

Yes, this trace bridging operates without additional dependencies, requiring only that you initialize Sentry before autotel and register the span processor to enable trace conversion and error linking.

Why are my OpenTelemetry spans not showing up as Sentry transactions?

OpenTelemetry spans may not appear as Sentry transactions if Sentry is not initialized before autotel or the span processor is not registered to facilitate the mapping of spans to transactions.

Do I need autotel to map OpenTelemetry spans to Sentry transactions?

Yes, when deploying a Node.js application, autotel works with Sentry to ensure traces and errors are linked in both systems, simplifying debugging and analysis through trace conversion and error context enrichment.