You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
REES now has Sentry error capture and release/source-map upload, but its event taxonomy is still lighter than the self-host runtime. Operators should be able to group and filter REES issues by route, analyzer, repo, release, deployment, and event type without relying on free-text log search.
Requirements
Define a small allowlist of REES Sentry tags and apply it consistently across route errors, unhandled exceptions, source-map upload failures, and analyzer degradation events.
Use stable fingerprints for known operational classes: source-map upload failure, analyzer degradation by analyzer, auth/config failure, and route-level exceptions.
Keep high-cardinality or sensitive values in sanitized context only, not tags.
Do not attach request bodies, diffs, authorization headers, tokens, or prompt/review content.
Part of #998. Related: #1732.
Context
REES now has Sentry error capture and release/source-map upload, but its event taxonomy is still lighter than the self-host runtime. Operators should be able to group and filter REES issues by route, analyzer, repo, release, deployment, and event type without relying on free-text log search.
Requirements
event,route,method,repo,pullNumber,analyzer,release,environment,railwayDeploymentId.Deliverables
review-enrichment/src/sentry.ts,review-enrichment/src/server.ts,review-enrichment/src/upload-sourcemaps.ts, and analyzer degradation capture from observability(rees): capture degraded analyzer runs in Sentry #1732 as applicable.Acceptance criteria