Use case
Deployment-error correlation connects an operational issue to a preceding release using available evidence. ShipTale prioritizes an exact commit match, then an explicit project mapping plus time, then a limited time-only fallback. It stores the correlation method and confidence, and leaves events unlinked when the evidence is insufficient.
A source marker or exact commit is strongest. A mapped resource combined with time proximity is useful but less conclusive. A nearest prior production release within 24 hours is a low-confidence fallback. This precedence prevents convenient timing from looking like proof.
ShipTale keeps an event outside a Tale when no eligible production release exists, the event falls outside the fallback window, or project evidence is insufficient. Unlinked is a valid outcome, not missing data to hide.
| Area | Supports | Does not claim or do |
|---|---|---|
| High confidence | Exact commit or release-source evidence | A guarantee of causation |
| Medium confidence | Mapped resource plus time proximity | Name similarity alone |
| Low confidence | Nearest prior release within 24 hours | Unlimited time matching |
Record a successful production deployment as the release marker.
Apply commit, mapping, and bounded time rules in precedence order.
Show the confidence label and preserve the method for later review.
Review imported issue context.
Apply correlation in a release workflow.
See the complete Tale model.
Connect Vercel and Sentry free. Add Stripe customer context on Pro.