sentry-setup-tracing

Name: sentry-setup-tracing
Availability: InStock
Author: Sentry

Configure Sentry tracing for JavaScript, Python, and Ruby projects.

246|29|Updated Nov 10, 2025

Search Tags:#performance #observability #tracing #transactions #sentry #spans

Ready to run

npx skills add https://github.com/getsentry/sentry-for-claude --skill sentry-setup-tracing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sentry-setup-tracing
Source: https://github.com/getsentry/sentry-for-claude/tree/main/skills/sentry-setup-tracing
Command: npx skills add https://github.com/getsentry/sentry-for-claude --skill sentry-setup-tracing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill configures Sentry Tracing to monitor application performance, measure latency, and enable distributed traces across services, reducing guesswork in performance tuning.

Core Features & Use Cases

Transaction & Span Setup: Instrument root transactions and nested spans for end-to-end visibility.
Platform Guidance: JavaScript/TypeScript, Python, Ruby setup guidance with example configurations.
Sampling & Propagation: Guidance on tracesSampleRate and trace propagation targets.

Quick Start

Add tracing to your Node.js API by enabling tracesSampleRate and a basic Browser/Server integration, then verify traces in Sentry.

Frequently Asked Questions about sentry-setup-tracing

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

FAQPage Schema

How do I enable performance tracing in Sentry to monitor application latency?▼

Enable performance tracing in Sentry by setting tracesSampleRate in your SDK initialization to capture a percentage of transactions, then instrument your application with spans to measure specific operations. This gives you visibility into end-to-end latency and bottlenecks across your services.

What's the difference between transactions and spans in Sentry tracing?▼

Transactions represent root-level operations like HTTP requests or page loads, while spans are nested child operations within transactions that measure specific tasks. Together they create a hierarchical trace showing where time is spent across your application.

Can I use Sentry tracing with Next.js, Node.js, and Python in the same distributed system?▼

Yes. Sentry tracing supports JavaScript/TypeScript (Next.js, Node.js, React, Vue, Angular, SvelteKit), Python, and Ruby with platform-specific setup. Trace propagation connects transactions across services so you see the complete request path through your distributed system.

How do I decide what tracesSampleRate to use for my application?▼

Set tracesSampleRate as a decimal between 0 and 1 to control what percentage of transactions Sentry captures. Start with a lower rate in production to manage volume, or use tracesSampler for dynamic sampling based on transaction context like URL or user tier.

What setup steps are required before I can start tracing transactions in my browser and server apps?▼

Initialize the Sentry SDK with tracing enabled, set tracesSampleRate or tracesSampler, and integrate framework-specific instrumentation for your platform (browser, Next.js, Node.js, etc.). Sentry automatically instruments common operations; verify traces appear in your Sentry dashboard.

Why would I need distributed tracing across multiple services?▼

Distributed tracing connects transactions across your frontend, backend, and microservices to show you the complete request flow and identify where performance degrades. This reduces guesswork in performance tuning and helps pinpoint bottlenecks that span multiple systems.