6.2.0

Add CustomTimestamp to EventContext

There are cases where you might want to override the event timestamp

6.0.8

Bug fix for AppendToValue (handle null values)

6.0.6

Breaking Changes

• Migration Guide
• Drop support for legacy .NET framework (net40)
• Require netstandard >= 2.0
• Custom logging signature now receives LogEvent rather than a raw string
• Unify initialization API across built in and custom providers

New Features

• Splunk provider
• Prometheus provider
• API for customizing timer behaviors

6.0.0

Breaking Changes

• Migration Guide
• Drop support for legacy .NET framework (net40)
• Require netstandard >= 2.0
• Custom logging signature now receives LogEvent rather than a raw string
• Unify initialization API across built in and custom providers

New Features

• Splunk provider
• Prometheus provider

5.2.0: Adds support for counting

Library has always had support for 'timing' subevents (i.e. granular timings [e.g. database query duration]), but didn't have support for simply counting (e.g. number of roundtrips to database)

5.1.1

Release Notes

• If multiple timings (EventContext.Time) are performed using the same key, accumulate total time elapsed

NLog 4.5.0

https://www.nuget.org/packages/Spiffy.Monitoring.NLog/4.5.0

5.1.0

Update Console and Trace implementations to route messages based on level (e.g. errors to Console.Error)

5.0.0

#10
#17
#18

4.0.4

Spiffy.Monitoring.4.0.4

Fixes #16