feat(tracing): add support for logs #840
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## lcian/ref/tracing #840 +/- ##
=====================================================
+ Coverage 73.40% 73.64% +0.23%
=====================================================
Files 64 64
Lines 7682 7728 +46
=====================================================
+ Hits 5639 5691 +52
+ Misses 2043 2037 -6 🚀 New features to boost your workflow:
|
lcian
commented
Jun 12, 2025
| } | ||
|
|
||
| attributes.insert("sentry.origin".to_owned(), "auto.tracing".into()); | ||
|
|
There was a problem hiding this comment.
Unfortunately we cannot get the sentry.message.template with tracing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds logs support for
sentry-tracing, gated by alogsfeature flag.Open question for the future:
Someone might want to capture multiple things (e.g. if you get an error event, capture both a Sentry error and an error level log).
I would like to implement this but without breaking changes.