docs: Sentry to @nais/apm migration guide#877
Merged
Conversation
This was referenced Jul 5, 2026
…+ quickstarts Centralize the PII/setUser rule and the Sentry-differences list on the `@nais/apm` API reference so guides cross-link instead of duplicating. - reference: rename "Known limitations (0.1.0)" to a version-free "Limitations & differences from Sentry" and make it the complete list (no event id, setTag-as-context, unsupported Sentry APIs, no source-map upload, preview replay). Expand "Privacy: PII scrubbing" with a canonical "setUser and user identity" section. Give InitOptions a real anchor. - migration guide: replace the long "What's different" / "Not yet supported" sections with a short "Differences from Sentry" that cross-links the reference; reduce Issues/Alerts/source-maps to one-liners with links. - quickstarts (Next.js, React+Vite): replace the repeated opaque-id/PII and server-side source-map explanations with one-liner cross-links; keep the framework-specific setup. - fix stale cross-link anchors into the reference (init options, captureException). - pin docs to @nais/apm@0.4.0.
Starefossen
force-pushed
the
docs/sentry-migration-guide
branch
from
2337143 to
ef7512c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a new nav-gated how-to: Migrate from Sentry to
@nais/apm(
docs/observability/frontend/how-to/migrate-from-sentry.md).This is a clean, full-migration guide — teams move off
@sentry/*entirelyonto idiomatic
@nais/apm. It is explicitly not a compatibility-shim guide.Contents
@nais/apmequivalent (init,captureException/captureMessage,setUser/setTag/setContext,ApmErrorBoundary/withApmErrorBoundary, route tracking, tracing, replay, sourcemap upload → server-side CDN, alerts → Grafana, Issues tab).initSentry.ts, Next.jsinstrumentation-client.ts+withSentryConfig).setUserPII drop (personvern), Grafana Issues tab triage model, server-side sourcemaps, Grafana alerts, events-tier replay default, and a plainly-stated not-yet-supported table.Flagged as not-yet-supported in the SDK
addBreadcrumb/beforeBreadcrumb, manual spans/transactions (startSpan/startTransaction), scopes (withScope/configureScope),setExtra/plural setters,lastEventId(),showReportDialog, profiling/release-health/attachments, and React Router v5/v7 + data routers.Notes
conditional: [tenant, nav]frontmatter.api.ts,index.ts,react/*,feedback.ts) and real navikt Sentry usage.nav+ssb; page renders for nav, is stripped for ssb, no leftover template tokens;tenant_urlmacro and internal links resolve.Draft — to be refined with usage-research findings.