Capture trace and span ids for Serilog 3.1 #227
Merged
Conversation
This file contains 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
|
Keeping this moving as part of the coordinated set of changes required to get feedback on trace/span support in Serilog 3.1. |
|
PSA for those who are just like me already trying to play with the new tracing in Serilog, this has indeed not been released yet. This means until this gets released and you rely on the Microsoft logging abstraction, you won't get any traces yet. |
Merged
Serilog 3.1 only supports log events - not traces. This feature adds trace and span ids to log events for correlation purposes. |
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.
See also serilog/serilog#1923, serilog/serilog-aspnetcore#207.
This will be best released in the v8.0 package version.