Serilog.Sinks.Console 6.0.0

Serilog.Sinks.Console Build status NuGet Version Documentation Help

A Serilog sink that writes log events to the Windows Console or an ANSI terminal via standard output. Coloring and custom themes are supported, including ANSI 256-color themes on macOS, Linux and Windows 10. The default output is plain text; JSON formatting can be plugged in using a package such as Serilog.Formatting.Compact.

Getting started

To use the console sink, first install the NuGet package:

dotnet add package Serilog.Sinks.Console

Then enable the sink using WriteTo.Console():

Log.Logger = new LoggerConfiguration()
    .WriteTo.Console()
    .CreateLogger();
    
Log.Information("Hello, world!");

Log events will be printed to STDOUT:

[12:50:51 INF] Hello, world!

Themes

The sink will colorize output by default:

Colorized Console

Themes can be specified when configuring the sink:

    .WriteTo.Console(theme: AnsiConsoleTheme.Code)

The following built-in themes are available:

  • ConsoleTheme.None - no styling
  • SystemConsoleTheme.Literate - styled to replicate Serilog.Sinks.Literate, using the System.Console coloring modes supported on all Windows/.NET targets; this is the default when no theme is specified
  • SystemConsoleTheme.Grayscale - a theme using only shades of gray, white, and black
  • AnsiConsoleTheme.Literate - an ANSI 256-color version of the "literate" theme
  • AnsiConsoleTheme.Grayscale - an ANSI 256-color version of the "grayscale" theme
  • AnsiConsoleTheme.Code - an ANSI 256-color Visual Studio Code-inspired theme
  • AnsiConsoleTheme.Sixteen - an ANSI 16-color theme that works well with both light and dark backgrounds

Adding a new theme is straightforward; examples can be found in the SystemConsoleThemes and AnsiConsoleThemes classes.

Output templates

The format of events to the console can be modified using the outputTemplate configuration parameter:

    .WriteTo.Console(
        outputTemplate: "[{Timestamp:HH:mm:ss} {Level:u3}] {Message:lj}{NewLine}{Exception}")

The default template, shown in the example above, uses built-in properties like Timestamp and Level. Properties from events, including those attached using enrichers, can also appear in the output template.

JSON output

The sink can write JSON output instead of plain text. CompactJsonFormatter or RenderedCompactJsonFormatter from Serilog.Formatting.Compact is recommended:

dotnet add package Serilog.Formatting.Compact

Pass a formatter to the Console() configuration method:

    .WriteTo.Console(new RenderedCompactJsonFormatter())

Output theming is not available when custom formatters are used.

XML <appSettings> configuration

To use the console sink with the Serilog.Settings.AppSettings package, first install that package if you haven't already done so:

dotnet add package Serilog.Settings.AppSettings

Instead of configuring the logger in code, call ReadFrom.AppSettings():

var log = new LoggerConfiguration()
    .ReadFrom.AppSettings()
    .CreateLogger();

In your application's App.config or Web.config file, specify the console sink assembly under the <appSettings> node:

<configuration>
  <appSettings>
    <add key="serilog:using:Console" value="Serilog.Sinks.Console" />
    <add key="serilog:write-to:Console" />

To configure the console sink with a different theme and include the SourceContext in the output, change your App.config/Web.config to:

<configuration>
  <appSettings>
    <add key="serilog:using:Console" value="Serilog.Sinks.Console" />
    <add key="serilog:write-to:Console.theme" value="Serilog.Sinks.SystemConsole.Themes.AnsiConsoleTheme::Code, Serilog.Sinks.Console" />
    <add key="serilog:write-to:Console.outputTemplate" value="[{Timestamp:HH:mm:ss} {Level:u3}] {Message:lj} &lt;s:{SourceContext}&gt;{NewLine}{Exception}" />

JSON appsettings.json configuration

To use the console sink with Microsoft.Extensions.Configuration, for example with ASP.NET Core or .NET Core, use the Serilog.Settings.Configuration package. First install that package if you have not already done so:

dotnet add package Serilog.Settings.Configuration

Instead of configuring the sink directly in code, call ReadFrom.Configuration():

var configuration = new ConfigurationBuilder()
    .AddJsonFile("appsettings.json")
    .Build();

var logger = new LoggerConfiguration()
    .ReadFrom.Configuration(configuration)
    .CreateLogger();

In your appsettings.json file, under the Serilog node, :

{
  "Serilog": {
    "WriteTo": [{"Name": "Console"}]
  }
}

To configure the console sink with a different theme and include the SourceContext in the output, change your appsettings.json to:

{
  "Serilog": {
    "WriteTo": [
      {
          "Name": "Console",
          "Args": {
            "theme": "Serilog.Sinks.SystemConsole.Themes.AnsiConsoleTheme::Code, Serilog.Sinks.Console",
            "outputTemplate": "[{Timestamp:HH:mm:ss} {Level:u3}] {Message:lj} <s:{SourceContext}>{NewLine}{Exception}"
          }
      }
    ]
  }
}

Performance

Console logging is synchronous and this can cause bottlenecks in some deployment scenarios. For high-volume console logging, consider using Serilog.Sinks.Async to move console writes to a background thread:

// dotnet add package serilog.sinks.async

Log.Logger = new LoggerConfiguration()
    .WriteTo.Async(wt => wt.Console())
    .CreateLogger();

Contributing

Would you like to help make the Serilog console sink even better? We keep a list of issues that are approachable for newcomers under the up-for-grabs label. Before starting work on a pull request, we suggest commenting on, or raising, an issue on the issue tracker so that we can help and coordinate efforts. For more details check out our contributing guide.

When contributing please keep in mind our Code of Conduct.

Detailed build status

Branch AppVeyor Travis
dev Build status Build Status
main Build status Build Status

Copyright © Serilog Contributors - Provided under the Apache License, Version 2.0.

Showing the top 20 packages that depend on Serilog.Sinks.Console.

Packages Downloads
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
43
Nuke.Common
Cross-platform build automation system Signed by signpath.io from repository 'https://github.com/nuke-build/nuke' commit '39132f3fb1fea9f889894dfe520cf4434d6eca4e' (see contained AppVeyorSettings.json file for build settings).
33
Nuke.Common
Cross-platform build automation system Signed by signpath.io from repository 'https://github.com/nuke-build/nuke' commit '4a24cd4e78d43b59deb8aa2033c696c8ceb51dd6' (see contained AppVeyorSettings.json file for build settings).
31
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
27
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
26
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
25
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
23
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
22
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
21
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
20
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
19
Nuke.Common
Cross-platform build automation system Signed by signpath.io from repository 'https://github.com/nuke-build/nuke' commit '12a091bbe2dc56bb3a2db64178dfc5305d769b3b' (see contained AppVeyorSettings.json file for build settings).
19
Nuke.Common
Cross-platform build automation system Signed by signpath.io from repository 'https://github.com/nuke-build/nuke' commit 'e20ab8d0fee05d3e1d1b6270a8e8a7967202eea9' (see contained AppVeyorSettings.json file for build settings).
18
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
18

.NET Framework 4.6.2

.NET Framework 4.7.1

.NET 6.0

.NET 8.0

.NET Standard 2.0

Version Downloads Last updated
6.0.0 8 06/17/2024
6.0.0-dev-00946 4 06/24/2024
5.1.0-dev-00943 13 03/30/2024
5.0.2-dev-00942 15 03/30/2024
5.0.1 8 02/19/2024
5.0.1-dev-00928 8 02/16/2024
5.0.0 6 02/20/2024
5.0.0-dev-00923 10 02/10/2024
4.2.0-dev-00918 4 02/10/2024
4.1.1-dev-00917 9 02/11/2024
4.1.1-dev-00910 33 04/02/2023
4.1.1-dev-00907 42 05/29/2023
4.1.1-dev-00901 15 08/28/2023
4.1.1-dev-00896 9 12/27/2023
4.1.0 27 09/14/2023
4.1.0-dev-00893 6 08/31/2023
4.0.2-dev-00890 8 09/01/2023
4.0.1 16 03/29/2023
4.0.1-dev-00879 5 08/25/2023
4.0.1-dev-00876 12 08/31/2023
4.0.1-dev-00874 5 08/27/2023
4.0.0 58 09/10/2021
4.0.0-dev-00870 21 08/28/2023
4.0.0-dev-00839 4 08/30/2023
4.0.0-dev-00837 21 08/25/2023
4.0.0-dev-00834 9 08/25/2023
4.0.0-dev-00832 11 08/31/2023
4.0.0-dev-00831 13 08/27/2023
3.1.2-dev-00824 30 08/30/2023
3.1.2-dev-00823 6 08/31/2023
3.1.2-dev-00819 6 02/16/2024
3.1.2-dev-00811 20 05/18/2023
3.1.2-dev-00806 7 08/26/2023
3.1.2-dev-00802 20 08/27/2023
3.1.2-dev-00800 6 08/31/2023
3.1.2-dev-00798 5 08/31/2023
3.1.2-dev-00796 6 08/25/2023
3.1.2-dev-00792 8 08/30/2023
3.1.2-dev-00788 6 08/26/2023
3.1.2-dev-00786 6 08/26/2023
3.1.2-dev-00779 6 08/29/2023
3.1.2-dev-00777 9 08/29/2023
3.1.2-dev-00774 11 02/16/2024
3.1.2-dev-00771 14 05/18/2023
3.1.1 59 12/27/2019
3.1.1-dev-00764 11 02/16/2024
3.1.1-dev-00762 6 08/27/2023
3.1.1-dev-00757 8 08/24/2023
3.1.0 24 06/13/2023
3.0.2-dev-00753 6 08/26/2023
3.0.1 20 09/21/2023
3.0.1-dev-00749 4 02/16/2024
3.0.1-dev-00747 34 05/17/2023
3.0.0 35 06/01/2023
3.0.0-dev-00737 11 08/24/2023
3.0.0-dev-00735 5 02/16/2024
3.0.0-dev-00734 10 08/25/2023
3.0.0-dev-00732 6 08/26/2023
2.2.0-dev-00721 7 08/25/2023
2.2.0-dev-00719 10 08/30/2023
2.1.0 80 06/02/2021
2.1.0-dev-00715 9 08/25/2023
2.1.0-dev-00713 18 09/04/2023
2.0.0 11 02/12/2024
2.0.0-rc-709 6 02/16/2024
2.0.0-beta-707 14 08/26/2023
2.0.0-beta-706 11 08/31/2023
2.0.0-beta-700 4 08/29/2023
2.0.0-beta-513 6 08/25/2023
2.0.0-beta-511 14 08/24/2023
2.0.0-beta-509 19 08/29/2023
2.0.0-beta-507 20 08/29/2023
2.0.0-beta-505 26 07/29/2023
2.0.0-beta-502 5 08/27/2023
2.0.0-beta-499 15 08/21/2023
2.0.0-beta-495 8 08/30/2023
2.0.0-beta-494 4 08/27/2023
2.0.0-beta-493 4 08/24/2023
2.0.0-beta-487 7 08/30/2023
2.0.0-beta-486 7 08/28/2023
2.0.0-beta-479 8 08/31/2023
2.0.0-beta-478 19 05/27/2023
2.0.0-beta-465 6 08/26/2023
2.0.0-beta-456 15 08/30/2023
2.0.0-beta-450 14 08/27/2023
2.0.0-beta-449 24 06/06/2023