The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
dotnet add package Akka.Logger.Serilog --version
NuGet\Install-Package Akka.Logger.Serilog -Version
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Akka.Logger.Serilog" Version="" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Akka.Logger.Serilog --version
#r "nuget: Akka.Logger.Serilog,"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Akka.Logger.Serilog as a Cake Addin
#addin nuget:?package=Akka.Logger.Serilog&version=

// Install Akka.Logger.Serilog as a Cake Tool
#tool nuget:?package=Akka.Logger.Serilog&version=


This is the Serilog integration plugin for Akka.NET. Please check out our documentation on how to get the most out of this plugin.

Targets Serilog 2.12.0.

Semantic Logging Syntax

If you intend on using any of the Serilog semantic logging formats in your logging strings, you need to use the SerilogLoggingAdapter inside your instrumented code or there could be elsewhere inside parts of your ActorSystem:

var log = Context.GetLogger<SerilogLoggingAdapter>(); // correct
log.Info("My boss makes me use {semantic} logging", "semantic"); // serilog semantic logging format


var log = MyActorSystem.GetLogger<SerilogLoggingAdapter>(myContextObject); // correct
log.Info("My boss makes me use {semantic} logging", "semantic"); // serilog semantic logging format


var log = MyActorSystem.GetLogger<SerilogLoggingAdapter>(contextName, contextType); // correct
log.Info("My boss makes me use {semantic} logging", "semantic"); // serilog semantic logging format

This will allow all logging events to be consumed anywhere inside the ActorSystem, including places like the Akka.NET TestKit, without throwing FormatExceptions when they encounter semantic logging syntax outside of the SerilogLogger.

Adding Property Enricher To Your Logs

Default Properties

You can add property enrichers to the logging adapter that will be added to all logging calls to that logging adapter.

var log = Context.GetLogger<SerilogLoggingAdapter>()
    .ForContext("Address", "No. 4 Privet Drive")
    .ForContext("Town", "Little Whinging")
    .ForContext("County", "Surrey")
    .ForContext("Country", "England");
log.Info("My boss makes me use {Semantic} logging", "semantic");

All logging done using the log ILoggingAdapter instance will append "Address", "Town", "County", and "Country" properties into the Serilog log.

One-off Properties

You can add one-off property to a single log message by appending PropertyEnricher instances at the end of your logging calls.

var log = Context.GetLogger<SerilogLoggingAdapter>();
    "My boss makes me use {Semantic} logging", "semantic",
    new PropertyEnricher("County", "Surrey"), 
    new PropertyEnricher("Country", "England"));

This log entry will have "County" and "Country" properties added to it.

Building this solution

To run the build script associated with this solution, execute the following:


c:\> build.cmd all

Linux / OS X

c:\> build.sh all

If you need any information on the supported commands, please execute the build.[cmd|sh] help command.

This build script is powered by FAKE; please see their API documentation should you need to make any changes to the build.fsx file.


The attached build script will automatically do the following based on the conventions of the project names added to this project:

  • Any project name ending with .Tests will automatically be treated as a XUnit2 project and will be included during the test stages of this build script;
  • Any project name ending with .Tests will automatically be treated as a NBench project and will be included during the test stages of this build script; and
  • Any project meeting neither of these conventions will be treated as a NuGet packaging target and its .nupkg file will automatically be placed in the bin\nuget folder upon running the build.[cmd|sh] all command.

DocFx for Documentation

This solution also supports DocFx for generating both API documentation and articles to describe the behavior, output, and usages of your project.

All of the relevant articles you wish to write should be added to the /docs/articles/ folder and any API documentation you might need will also appear there.

All of the documentation will be statically generated and the output will be placed in the /docs/_site/ folder.

Previewing Documentation

To preview the documentation for this project, execute the following command at the root of this folder:

C:\> serve-docs.cmd

This will use the built-in docfx.console binary that is installed as part of the NuGet restore process from executing any of the usual build.cmd or build.sh steps to preview the fully-rendered documentation. For best results, do this immediately after calling build.cmd buildRelease.

Release Notes, Version Numbers, Etc

This project will automatically populate its release notes in all of its modules via the entries written inside RELEASE_NOTES.md and will automatically update the versions of all assemblies and NuGet packages via the metadata included inside common.props.

If you add any new projects to the solution created with this template, be sure to add the following line to each one of them in order to ensure that you can take advantage of common.props for standardization purposes:

<Import Project="..\common.props" />
Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
  • .NETStandard 2.0

NuGet packages (3)

Showing the top 3 NuGet packages that depend on Akka.Logger.Serilog:

Package Downloads

SharpPulsar is Apache Pulsar Client built using Akka.net


An event source stack based on NEventStore and Akka


SDK for Sneaks&Data OSS Projects

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated 140,349 9/14/2023
1.5.12 9,900 8/31/2023
1.5.7 132,141 5/19/2023 56,832 3/15/2023
1.5.0 29,991 3/2/2023
1.5.0-beta5 256 3/1/2023
1.4.42 203,044 9/23/2022
1.4.26 397,163 10/7/2021
1.4.25 16,286 9/9/2021
1.4.17 158,106 3/17/2021
1.4.11 240,533 11/7/2020
1.4.10 11,344 10/28/2020
1.4.8 95,470 7/1/2020
1.4.3 57,951 3/27/2020
1.4.1 5,383 3/11/2020
1.4.1-rc3 394 3/10/2020
1.4.1-RC1 497 3/2/2020
1.3.11 44,169 2/5/2020
1.3.10 88,829 10/5/2019
1.3.9 289,867 8/23/2018
1.3.6 92,481 4/30/2018
1.3.3 44,111 2/1/2018
1.3.0 28,454 8/15/2017
1.2.0 14,631 5/2/2017
1.1.3 5,556 2/15/2017
1.1.2 10,207 10/11/2016
1.1.1 5,514 7/16/2016
1.0.8 10,733 4/28/2016
1.0.7 1,713 4/7/2016
1.0.6 4,301 1/18/2016
1.0.5 2,313 12/3/2015
1.0.4 3,066 8/8/2015
1.0.3 1,749 6/12/2015
1.0.2 1,361 6/3/2015
1.0.1 1,772 4/28/2015
1.0.0 1,377 4/9/2015
1.0.0-dev1504032244 1,061 4/3/2015
0.8.0 1,573 2/12/2015
0.7.1 1,575 12/13/2014
0.7.0 2,576 10/20/2014