Files
Evan Purkhiser 64dfeaa1f1 ref(skills): move superseded skills to skills-legacy (#265)
These per-SDK skills, plus a handful of setup/workflow skills, are superseded
by the sentry-instrument skill and the references/sdks/ trees. Move them under
skills-legacy/ so they are excluded from the plugin build and skipped by the
drift automation, while skills.sentry.dev can still serve them as a fallback
for existing URL consumers.

Moves 26 skills: the 19 per-SDK skills plus sentry-sdk-skill-creator,
sentry-fix-issues, the three sentry-span-streaming-* skills,
sentry-instrument-logging, and sentry-instrumentation-guide. Regenerates
SKILL_TREE.md and repaths the moved entries in CODEOWNERS.

sentry-sdk is intentionally left in place; its removal is handled in a
separate PR.
2026-07-10 11:51:09 -04:00

1.4 KiB

Profiling — Sentry React Router Framework SDK

Minimum SDK: @sentry/react-router with @sentry/profiling-node for server profiling


Profiling setup (server)

Install profiling package:

npm install @sentry/profiling-node --save

Configure in instrument.server.mjs:

import * as Sentry from "@sentry/react-router";
import { nodeProfilingIntegration } from "@sentry/profiling-node";

Sentry.init({
  dsn: "___PUBLIC_DSN___",
  integrations: [nodeProfilingIntegration()],
  tracesSampleRate: 1.0,
  profileSessionSampleRate: 1.0,
});

Sampling strategy

Setting Purpose
tracesSampleRate How many transactions are captured
profileSessionSampleRate What fraction of traced transactions get profiles

Start high in development, then lower for production cost control.


Verification

  1. Trigger a server transaction with profiling enabled.
  2. Open Profiles in Sentry.
  3. Confirm profile entries appear and are linked to transactions.

Troubleshooting

Issue Solution
No profiles visible Ensure @sentry/profiling-node is installed and integration is active
Traces visible but no profiles Increase profileSessionSampleRate
Profile volume too high Lower profileSessionSampleRate and/or tracesSampleRate
Runtime incompatibility symptoms Verify Node runtime support and fallback to tracing-only where needed