Sentry integration
ShipTale reads selected Sentry projects and the issue changes needed for a post-deployment timeline. It can associate those events with a Vercel release using an exact commit, an explicit project mapping plus time, or a qualified time-only fallback. Every association keeps a confidence label instead of presenting correlation as proof of causation.
Last reviewed:
ShipTale stores normalized issue-change context required by the timeline, including occurrence time, project identity, severity, title, and correlation evidence. It does not retain Sentry stack traces, breadcrumbs, or attachments.
An exact commit match is high confidence. A configured Sentry-to-Vercel project mapping plus time is medium confidence. A nearest preceding production release within the 24-hour fallback window is low confidence. Events without defensible evidence stay unlinked.
| Area | Supports | Does not claim or do |
|---|---|---|
| Access | Read organizations, selected projects, issues, and project stats | Editing or resolving issues in Sentry |
| Retained detail | Normalized issue-change and correlation fields | Stack traces, breadcrumbs, or attachments |
| Claims | Explainable association with confidence | Claiming a deployment caused an issue |
Use an Internal Integration Auth Token with the documented read permissions.
Choose Sentry projects and map them to Vercel projects when names or ownership differ.
Use the confidence label and provider link before deciding how to respond.
These primary sources describe provider capabilities. ShipTale behavior is described separately above.
Use production deployments as release anchors.
See how confidence is assigned.
Review credential and retention controls.
Connect Vercel and Sentry free. Add Stripe customer context on Pro.