-
Notifications
You must be signed in to change notification settings - Fork 901
Add ExtendedLogRecordBuilder#setException #7182
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
Add ExtendedLogRecordBuilder#setException #7182
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7182 +/- ##
============================================
- Coverage 89.98% 89.97% -0.02%
- Complexity 6685 6689 +4
============================================
Files 749 749
Lines 20191 20200 +9
Branches 1977 1977
============================================
+ Hits 18168 18174 +6
- Misses 1431 1433 +2
- Partials 592 593 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
sdk/trace/src/test/java/io/opentelemetry/sdk/trace/SdkSpanTest.java
Outdated
Show resolved
Hide resolved
Per conversation in the 4/10/25 java SIG, I've broken out the configurable exception.* attribute value resolution into a separate PR, #7266. |
See comment
exception.*
. Standardizing in the SDK "DRY"s up the instrumentation code, and provides a more familiar log API experience.Makesee commentexception.*
resolution configurable -exception.*
attributes are now resolved and attached to both span events and log records. This is an edge cases where the SDK specification has a dependency on the semantic conventions. It seems appropriate to make this a configurable extension point, so that users can customize things like theexception.stacktrace
resolution.