-
Notifications
You must be signed in to change notification settings - Fork 443
feat(tracer): deprecate escaped and timestamp attributes in record_exception API #13798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Circular import analysis🚨 New circular imports detected 🚨The following circular imports among modules have been detected on this PR, when compared to the base branch:
Please consider refactoring your changes in accordance to the Separation of Concerns principle. |
|
Bootstrap import analysisComparison of import times between this PR and base. SummaryThe average import time from this PR is: 278 ± 5 ms. The average import time from base is: 281 ± 5 ms. The import time difference between this PR and base is: -3.4 ± 0.2 ms. Import time breakdownThe following import paths have grown:
|
BenchmarksBenchmark execution time: 2025-06-30 16:09:47 Comparing candidate commit 29a9ec1 in PR branch Found 0 performance improvements and 6 performance regressions! Performance is the same for 564 metrics, 2 unstable metrics. scenario:iastaspects-format_map_aspect
scenario:iastaspectsospath-ospathbasename_aspect
scenario:iastaspectsospath-ospathjoin_aspect
scenario:iastaspectsospath-ospathnormcase_aspect
scenario:iastaspectsospath-ospathsplitdrive_aspect
scenario:telemetryaddmetric-1-distribution-metric-1-times
|
9543c09
to
7bc2491
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some non blocking suggestions. Overall looks good to me 😄
Motivation
record_exception
call was added few releases ago because some customers were asking to be able to send manually errors. However, it was mainly based on the OpenTelemetry implementation. The OTEL sdk are inconsistent between tracers and some implementations are using for exampleescaped
attribute which does not make sense at all for us.An RFC was written to ease the implementation across tracer. This PR is there to make the python implementation consistent with the RFC.
Changes
escaped
andtimestamp
attributesrecord_exception
doc.Checklist
Reviewer Checklist