Sentry: Incomplete Stack Traces
Timeline of updates
- resolved
Between Mon 2021-07-12 16:27 UTC and Thu 2021-07-15 11:00 UTC a Symbolicator version was deployed which was incorrectly timing out early during the fetching of some Debug Information Files (DIFs). All symbol sources were affected and this resulted in stack traces being created with some missing information, resulting in some partial stack traces or missing symbolication. The issue is now resolved and if needed reprocessing the issue will correctly fetch the DIFs and use them in symbolication.
From Sentry’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.sentry.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Sentry, started 2021-07-12 16:27 UTC, resolved after 0 min, 1 update(s).
- Title
- Incomplete Stack Traces
- Vendor
- Sentry
- Date
- URL
- https://rewindex.com/company/sentry/incidents/12ffnq09nmqk
Sentry profileRecent Sentry incidentsAll outages on July 12, 2021Sentry in July 2021MarkdownJSON