[EPIC] Tag Errors with Full Traces

[matejminar]

Problem: Because of transaction sampling, we are “losing” the tie between traces and issues. This correlation is a valued feature for customers in their investigation process.

Proposed Solution: Tag recent Errors that are included in full traces, so that the UI can prioritise displaying these in the issue details page. Initiative tech spec.

Expected Outcome: Ensure the availability of traces and display them in the UI whenever a correlation is possible*.

*Note: Missing or incomplete traces can be caused by a series of other factors including client-side sampling, rate limits and running out of quota. We are focusing on resolving exclusively the problems created by server-side sampling.

Notion Doc: https://www.notion.so/sentry/Tag-errors-with-full-traces-36bf9e977eb04b99b482d09b82e6a60f

Milestone 1 - Internal

Beta Give feedback

1. [SPIKE] Investigate with SNS how to properly store the new flag #47152
   Status: Stale +1
   
2. [SPIKE] Explore how to integrate "fake" dynamic sampling into error processing #47153
   Status: Stale +1
   
3. Start flagging errors with traces in Relay #48773
   +0
   
4. Start indexing the new flag #48774
   +0
   

Milestone 1 - EA

Beta Give feedback

1. EA

Milestone 1 - GA

Beta Give feedback

1. GA
2. SDKs Need to Forward DSC on error events team-webplatform-meta#45
   Grooming +1
3. Investigate why sentry python project does not have the flag #49933
   Status: Stale +1
   

[iambriccardo]

[iambriccardo]

getsentry/team-webplatform-meta#45

[iambriccardo]

@antonpirker wrote me that on Python it is supported from https://github.com/getsentry/sentry-python/releases/tag/1.20.0.

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀