Set up Sentry error tracking with release health and source maps

domain: sentry.io · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Init SDK with dsn, environment, release (git SHA), tracesSampleRate
  2. Upload source maps at build time (sentry-cli sourcemaps upload or bundler plugin) tied to the same release
  3. Set user context (sentry.setUser) for impact triage
  4. Alert rules on issue volume + new-issue-in-release

Known gotchas

Related routes

Record a Sentry deploy for a release via the API to track release health per environment
docs.sentry.io · 5 steps · unrated
Create a Sentry release and upload JavaScript sourcemaps via the API
docs.sentry.io · 5 steps · unrated
Track Sentry release performance with transaction monitoring and compare p75 latency across releases using the Sentry performance dashboard
sentry.io · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans