fix(webapp): collapse Prisma P1001 errors into a single Sentry issue

[d-cs]

Summary

• Adds a beforeSend rule in apps/webapp/sentry.server.ts that collapses Prisma P1001 ("Can't reach database server") errors into a single Sentry issue regardless of which call site threw, by setting event.fingerprint = ["prisma-p1001-db-unreachable"] and tagging db_unreachable:true.
• Matches both err.code === "P1001" (Prisma's KnownRequestError when a connection drops mid-query) and err.errorCode === "P1001" (InitializationError when the client fails to connect at startup).
• Implemented as a small extensible FINGERPRINT_RULES table so further fan-out errors can be added with one entry.

Verification

End-to-end verified locally with debug: true on the SDK:

• Real Prisma P1001 thrown from a loader (DB stopped mid-request) is captured by Sentry's Remix auto-instrumentation
• beforeSend fires with originalException.code === "P1001", rule matches
• event.fingerprint = ["prisma-p1001-db-unreachable"] and tags.db_unreachable = "true" applied
• Event lands in Sentry under the new fingerprint

Test plan

• Deploy to staging; confirm P1001 events appear under a single prisma-p1001-db-unreachable issue rather than fanning out
• Confirm db_unreachable:true tag is filterable in Sentry
• Verify non-P1001 errors are unaffected (event passes through beforeSend untouched)

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 40e07f5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

This change introduces Sentry fingerprint-based grouping for Prisma P1001 database connectivity errors. A new FINGERPRINT_RULES configuration constant defines rules that match P1001 errors via either code or errorCode and assign a fixed fingerprint identifier along with a db_unreachable tag. A beforeSend hook is added to the Sentry init configuration that extracts the original exception from the event hint, matches it against the rules, and when a match is found, sets the event's fingerprint and merges the rule's tags into the event. Documentation is added to describe the change and note the extensible rule table for future collapsing rules.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is largely incomplete compared to the repository template. While it provides thorough technical details about the change and verification, it is missing required checklist items and does not follow the template structure with sections for Testing, Changelog, and Screenshots.	Complete the PR description by adding the required checklist section with checkboxes, a dedicated Testing section with concrete steps, and a Changelog section. Include the Screenshots section even if empty.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and clearly describes the main change: collapsing Prisma P1001 errors into a single Sentry issue, which matches the primary objective of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sentry-db-unreachable-fingerprint

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.