feat: do not report error stack for status code errors#3837
Conversation
BenchmarksBenchmark execution time: 2025-09-24 14:35:03 Comparing candidate commit 4fefb03 in PR branch Found 0 performance improvements and 1 performance regressions! Performance is the same for 2 metrics, 0 unstable metrics. scenario:BenchmarkSetTagStringPtr-24
|
| ErrorStack = "error.stack" | ||
|
|
||
| // ErrorHandlingStack specifies the stack dump when the error is captured. | ||
| ErrorHandlingStack = "error.handling_stack" |
There was a problem hiding this comment.
We are adding these two new tags, what are the implications on the ingestion side? Especially for error tracking?
There was a problem hiding this comment.
The new tags will change the behavior of error tags on spans; handling_stack should already be handled from the error tracking side, but we just haven't been taking advantage of it earlier. The fingerprints of spans will change after we release this PR, so we should give them a heads-up before so that they can adjust in the backend.
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
devflow unqueued this merge request: It did not become mergeable within the expected time |
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
ErrorNoStackTrace, to report errors without capturing the stack trace for our UI.error.stacktoerror.handling_stack, movingerror.detailsintoerror.stack, and deprecatingerror.details.Motivation
We were creating errors and reporting the stack for status code errors. For new error stack features (#3709), this causes us to create two error stacks: one starting from
SetTagand one started from error creation. To avoid this, and also because reporting these error stacks is superfluous, we want to prevent reporting these stacks to hide them from our UI.For information on what each tag represents, refer to this (internal) page.
IMPORTANT: this might be considered a breaking change for Error Tracking. Please check with the ET team before releasing this feature.
Reviewer's Checklist
./scripts/lint.shlocally.Unsure? Have a question? Request a review!