Vostok.Logging
HomeQuickstartModulesImplementations
1.0.0
1.0.0
  • Home
  • Quickstart
  • Guarantees
  • Configuration
  • Concepts and basics
    • Log interface
    • Log events
    • Syntax
      • Logging extensions
      • Message templates
      • Providing property values
    • Formatting
      • Output templates
      • Special properties
      • Format specifiers
    • Source context
    • Operation context
  • Modules
    • Abstractions
    • Configuration
    • Formatting
    • Console
    • File
    • Hercules
    • Context
    • Serilog
    • Log4net
    • NUnit
    • Microsoft
  • Implementations
    • Silent log
    • Console log
    • File log
    • Hercules log
  • Integrations
    • Serilog integration
    • Log4net integration
    • Microsoft logging integration
  • How-to guides
    • Using operation context
    • Using static log provider
    • Filtering events
    • Enriching events
    • Transforming events
    • Combining multiple logs
    • Custom output templates
    • External configuration rules
Powered by GitBook
On this page

Home

NextQuickstart

Last updated 6 years ago

CtrlK
  • Vostok.Logging in a nutshell
  • Guiding design principles
  • Features
  • Good starting points

Vostok.Logging in a nutshell

Vostok.Logging is a set of libraries providing structured logging for .NET applications, much like Serilog, but tightly integrated into Vostok ecosystem.

Guiding design principles

  • Logging system should not be able to significantly impact application health or performance.

    • Guarantees section covers this topic in greater detail.

  • Configuration is done in code.

    • Configuring and composing loggers in code is preferable to clumsy XML files. See Configuration section for an in-depth discussion.

  • Extensibility is valued.

    • The libraries are designed in a way that encourages creating custom implementations of logs and decorators.

  • Performance is of essence.

    • Implementations go to great lengths to provide a throughput level sufficient for applications handling tens or even hundreds of thousands of requests per second.

Features

  • Structured logging

    • Log events contain key-value properties which are later used for querying the log data or rendering it to text.

  • Reliable built-in log implementations

    • , and logs comply to strict and offer solid performance.

  • Easy configuration

    • Most log implementations require just one line of code to set up (see ).

  • Customizable formatting

    • Output produced by text-based logs ( and ) can be customized with .

  • Filtering of log events

    • There's built-in support for by level, properties or arbitrary contents of .

  • Enrichment of log events with custom properties

    • Log events can be dynamically with new properties either specified by user or provided from ambient context.

  • Support for contextual information tied to log events

    • Explore the and context sections to learn more.

  • Integrations with other popular logging libraries

    • There are adapters available for , and .

Good starting points

Quickstart
Modules
Log interface
Log events
Syntax
Console
file
Hercules
guarantees
Quickstart
console
file
output templates
filtering
log events
enriched
source
operation
Serilog
log4net
Microsoft.Extensions.Logging