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.
This PR contains the following updates:
3.1.1
->4.0.0
2.3.0
->3.0.0
2.0.2
->3.0.0
3.1.0
->4.0.0
1.5.0
->2.0.0
5.0.1
->6.0.0
2.0.0
->3.0.0
Release Notes
serilog/serilog (Serilog)
v4.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.Channels
and draws on the originalSerilog.Sinks.PeriodicBatching
package (now in maintenance-mode), to provide a full-featured, efficient, async-native batching implementation.Experimental dotted name capturing
By setting an experimental
AppContext
switch, 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
UtcTimestamp
as a built-in token in output templates (@MatthewHays)ReusableStringWriter
(@nblumhardt)LogEvent.UnstableAssembleFromParts()
(@nblumhardt)IBatchedLogEventSink
andWriteTo.Sink(IBatchedLogEventSink)
(@nblumhardt)LoggerSinkConfiguration.CreateSink()
and redesign.Wrap()
(@nblumhardt, @bartelink)MessageTemplateParser
performance, switch to allow.
in captured property names (@nblumhardt)}
in message template format specifiers (@Insomniak47)serilog/serilog-enrichers-environment (Serilog.Enrichers.Environment)
v3.0.0
Breaking changes
The
*Enricher
types previously published in this assembly are now internal. These all haveEnrich.With*
configuration syntax alternatives; so, if your code usedEnrich.With(new EnvironmentNameEnricher(...))
, replace this withEnrich.WithEnvironmentName(...)
and so on.serilog/serilog-enrichers-process (Serilog.Enrichers.Process)
v3.0.0
Environment.ProcessId
where available (@Numpsy)serilog/serilog-enrichers-thread (Serilog.Enrichers.Thread)
v4.0.0
serilog/serilog-sinks-async (Serilog.Sinks.Async)
v2.0.0
WriteTo.Async()
overloads, drop pre-netstandard2.0
TFMs (@nblumhardt)serilog/serilog-sinks-console (Serilog.Sinks.Console)
v6.0.0
NO_COLOR
environment variable (@sungam3r)serilog/serilog-sinks-debug (Serilog.Sinks.Debug)
v3.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.