3.1.0 Release #1975
Merged
3.1.0 Release #1975
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
* Modernize the README a little more * Improve example Co-authored-by: C. Augusto Proiete <augusto@proiete.com> --------- Co-authored-by: C. Augusto Proiete <augusto@proiete.com>
… fix error when building without FEATURE_ITUPLE (#1960)
* Removed temporary array allocations for cases with the small number of log event properties * Added test to ensure that null array does not break message template parameters binding * Excluded ILogger.Write<T1, ...> methods from method body comparison test.
* By reference string comparison in template cache * Removed by-value template cache
* Trim dead PropertyGroup * Trim test TFMs
* Remove gitter from CONTRIBUTING.md * Remove year from copyright * Add Copyright prop for package * CloseAndFlushAsync comment * More shepherding to SO
|
Planning to merge this tomorrow (9th Nov.), so that any kinks in 3.1 can be ironed out before the .NET 8 *.Extensions packages go out next week. |
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.
CHANGES.md(@sungam3r)README.mdupdates (@nblumhardt)GetTypeInfo()calls (@SimonCropp)Logger.Write()(@epeshk)LogEvent#1955 breaking - collect and propagateActivity.Current.TraceIdandSpanIdautomatically inLogger.Write()(@nblumhardt)README.mdupdates (@bartelink)Built-in trace and span id support
This release adds two new first-class properties to
LogEvent:TraceIdandSpanId. These are set automatically inLogger.Write()to the corresponding property values fromSystem.Diagnostics.Activity.Current.The major benefit of this change is that sinks, once updated, can reliably propagate trace and span ids through to back-ends that support them (in much the same way that first-class timestamps, messages, levels, and exceptions are used today).
The sinks maintained under
serilog/serilog, along with formatting helpers such as Serilog.Formatting.Compact and Serilog.Expressions, are already compatible with this change or have pending releases that add compatibility.Breaking change
Trace and span id collection includes support for
{TraceId}and{SpanId}placeholders in output templates (commonly used when formatting text log files). Where previously these names resolved to user-defined properties, they now resolve to the built-inLogEvent.TraceIdandLogEvent.SpanIdvalues, respectively.Impact is expected to be low, because the trace and span id values in any user-added properties are likely to be identical to the built-in ones.