Bump Serilog and Serilog.Extensions.Logging #3
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.
Updated Serilog from 3.0.0 to 4.2.0.
Release notes
Sourced from Serilog's releases.
4.2.0
What's Changed
RuntimeHelpers.GetHashCode()in message template cache comparer (@sungam3r)net9.0TFM (@nblumhardt)ILogEventSink(@erichiller)New Contributors
Full Changelog: serilog/serilog@v4.1.0...v4.2.0
4.1.0
BatchingOptions.RetryTimeLimitand update retry scheduling algorithm (@nblumhardt)Important note
IBatchedLogEventSinkbatch retry scheduling has changed in this version. The default configuration still tries failed batches for approximately ten minutes, but theBufferingTimeLimitno longer implicitly causes the retry time to be extended or reduced. If you need a specific retry time, setBatchingOptions.RetryTimeLimit, which reliably controls retry time.4.0.2
getaccessors (@nblumhardt)IDisposableinLog.CloseAndFlushAsync()when the target logger is notIAsyncDisposable(@nblumhardt)4.0.1
HashSetinstances, reduce LINQ usage, avoid reallocatingstring[]to improve performance and cut GC pressure (@nblumhardt)Major.Minor.0.0assembly versioning (@nblumhardt)4.0.0
What's new in Serilog 4.0.0?
Simple, robust, built-in batching support
Sinks that need batching functionality can now be easily written, without any additional package dependencies, by implementing
IBatchedLogEventSink:Batched sinks can be added using
WriteTo.Sink(IBatchedLogEventSink, ...)- they're given first-class consideration just like regular un-batched sinks.The built-in batching implementation is based on
System.Threading.Channelsand draws on the originalSerilog.Sinks.PeriodicBatchingpackage (now in maintenance-mode), to provide a full-featured, efficient, async-native batching implementation.Experimental dotted name capturing
By setting an experimental
AppContextswitch, message templates can be used to capture dotted names, which are required when using some logging schemas.While currently experimental and unsupported, this flag is intended to help the ecosystem evaluate and prepare for dotted name support in a future Serilog release.
Changes
UtcTimestampas a built-in token in output templates (@MatthewHays)ReusableStringWriter(@nblumhardt)LogEvent.UnstableAssembleFromParts()(@nblumhardt)IBatchedLogEventSinkandWriteTo.Sink(IBatchedLogEventSink)(@nblumhardt)LoggerSinkConfiguration.CreateSink()and redesign.Wrap()(@nblumhardt, @bartelink)MessageTemplateParserperformance, switch to allow.in captured property names (@nblumhardt)}in message template format specifiers (@Insomniak47)... (truncated)
3.1.1
ReusableStringWriterwith large renderings (@nblumhardt)This is a bugfix for release 3.1.0.
3.1.0
CHANGES.md(@sungam3r)README.mdupdates (@nblumhardt)GetTypeInfo()calls (@SimonCropp)Logger.Write()(@epeshk)Activity.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.Dropped .NET Core 2.1 and 3.0 support
On .NET Core 2.1 and 3.0, projects targeting Serilog 3.1+ will fail to build, with:
Affected consumers should continue to use Serilog 3.0 or earlier. See serilog/serilog#1983 for a discussion of this issue.
Technical breaking changes
Trace and span id placeholders
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/zero, because the trace and span id values in any user-added properties are almost certainly identical to the built-in ones.
nintandnuint(IntPtrandUIntPtr) handlingThese integer types were previously logged as structures. They're now correctly logged as scalars.
3.0.1
JsonFormatteroutput forrenderMessage = true(@nblumhardt)Commits viewable in compare view.
Updated Serilog.Extensions.Logging from 3.0.1 to 9.0.2.
Release notes
Sourced from Serilog.Extensions.Logging's releases.
9.0.2
What's Changed
Full Changelog: serilog/serilog-extensions-logging@v9.0.1...v9.0.2
9.0.1
What's Changed
New Contributors
Full Changelog: serilog/serilog-extensions-logging@v9.0.0...v9.0.1
9.0.0
What's Changed
{SourceContext}for MEL logger category (@DavidHopkinsFbr)ISupportExternalScopeinSerilogLoggerProvider(@david-obee)ValueTuplearguments toILogger.BeginScope()(@jimbojim1997)ITuplearguments toILogger.BeginScope()(@sungam3r)EventIdproperty cache improvements/optimization (@AndreReise)IAsyncDisposableon .NET 6+ (@agehrke)8.0.0
7.0.0
LogLevel.None(@0xced)@and$keys (@sungam3r)Microsoft.Extensions.Loggingv7 (@nblumhardt)3.1.0
EventIdthrough to logger providers (@david-driscoll)latestFeaturein global.json (@skomis-mm)FormattedLogValues(@nblumhardt)Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)