sentry-performance-monitoring

Instrument applications with Sentry transactions, spans, and distributed tracing.

187|20|Updated Nov 20, 2025

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

Ready to run

npx skills add https://github.com/TheBushidoCollective/han --skill sentry-performance-monitoring

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sentry-performance-monitoring
Source: https://github.com/TheBushidoCollective/han/tree/main/jutsu/jutsu-sentry/skills/performance-monitoring
Command: npx skills add https://github.com/TheBushidoCollective/han --skill sentry-performance-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill teaches how to instrument applications with Sentry transactions, spans, and performance insights.

Core Features & Use Cases

Transactions: Track high-level user flows.
Spans: Measure sub-operations within a transaction.
Distributed Tracing: Propagate trace context across services.

Quick Start

Initialize Sentry and start a transaction around a payment flow.

Frequently Asked Questions about sentry-performance-monitoring

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

FAQPage Schema

How do I measure application performance with transactions and spans?▼

Transactions track high-level user flows, while spans measure sub-operations within them. Initialize Sentry, wrap your code in a transaction, create child spans for specific operations, and capture timing and metadata automatically or manually to visualize performance bottlenecks across your application.

Can I trace performance across multiple services?▼

Yes, distributed tracing propagates trace context across services. Sentry automatically captures and links transactions and spans from frontend and backend codebases, allowing you to follow a single user request through your entire system and identify where latency occurs.

How do I set up Sentry performance monitoring in my application?▼

Initialize Sentry with your DSN, enable browser tracing integration if monitoring frontend code, configure sampling and profiling settings to control data volume, then wrap critical user flows in transactions. Sentry automatically instruments many operations; add manual spans for custom logic requiring measurement.

What's the difference between transactions and spans in performance monitoring?▼

Transactions represent complete user operations or requests; spans are nested measurements of individual tasks within a transaction. A payment flow is a transaction; database queries, API calls, and cache lookups are child spans that break down where time is spent.

Do I need to instrument every part of my code for performance monitoring?▼

No, Sentry automatically instruments many frameworks and libraries. Start with transactions around critical user flows, then add manual spans only where automatic instrumentation gaps exist or where custom business logic requires visibility into performance characteristics.

How do I control the volume of performance data Sentry collects?▼

Configure sampling rules to capture a percentage of transactions or filter by criteria like endpoint or user. Profiling settings let you enable or disable CPU and memory profiling separately, and you can set custom sampling functions to balance observability with data costs.