The ingestion pipeline clearly will miss occasional errors and they result in a single issue full of events with unsymbolicated traces. While this does not happen super often considering our scale of errors being ingested, it is nonetheless very annoying.
If you look at the provided link, you can see the last event has debug info with a debug id that is listed in the list of uploaded debug info files in Sentry as uploaded 2mo ago.
Expected Result
All traces with uploaded debug files are symbolicated, with none missing symbolication
Actual Result
Some events do not get symbolicated and it results in reopening a ticket every time it happens on a new version.
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
The ingestion pipeline clearly will miss occasional errors and they result in a single issue full of events with unsymbolicated traces. While this does not happen super often considering our scale of errors being ingested, it is nonetheless very annoying.
If you look at the provided link, you can see the last event has debug info with a debug id that is listed in the list of uploaded debug info files in Sentry as uploaded 2mo ago.
Expected Result
All traces with uploaded debug files are symbolicated, with none missing symbolication
Actual Result
Some events do not get symbolicated and it results in reopening a ticket every time it happens on a new version.
Product Area
Ingestion and Filtering
Link
https://dropbox.sentry.io/issues/5425338141/
DSN
No response
Version
No response