Serilog: Instrumentation that Works for You
summary
Serilog presents concrete features: message templates capture templates plus typed properties so logs render as text or JSON; @ destructuring serializes objects (opt-in) into structured fields; a 32-bit template hash gives stable event IDs. The ecosystem lists ~59 repos, ~209 contributors and ~2.5M package downloads, with ~100 sinks (Postgres, Seq, Application Insights, Splunk). Enrichers and LogContext attach correlation properties; sinks use a periodic-batching sender with exponential backoff. ASP.NET Core adopts the templates, and the pipeline is proven in production.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:04Design Goals
- 5:10Capturing Events with Message Templates
- 6:24Text Logging
- 20:55Structured Events
- 25:07Message Templates
- 29:13Event Types
- 33:03Enrichment
- 35:07Ambient Data
- 36:20Log Context
- 38:47Enrichment Toolkit
- 46:55Periodic Batching Sync
- 48:41Transactional Logging
related talks
59mSerilog: Instrumentation that Works for You
53mLogging Is Hot Again
54mLogging, Metrics and Events in ASP NET Core
01h 01mLogging, tracing and metrics: instrumentation in .NET and Azure
53m.NET:Stay calm and Serilog + Elastic Search + Kibana on .NET Core
41mIntroducing logs in OpenTelemetry: Features and opportunities
01h 00mPractical OpenTelemetry for .NET
29mAre logs a software engineer's best friend? Yes - follow these best practices