Custom logging

Experienced users (familiar with .NET development) can configure logging to fit their needs using Serilog configuration file. This file must be named logging.json and located in the configuration directory.

logging: { useCustomConfig: true } must be set in the config.yaml configuration file.

Any library dependencies not included in the release must be copied from e.g. nuget.org to the installation directory (where other Serilog.*.dll files are located), including their transitive dependencies. Extra care should be taken to ensure that the supplied dll files are compatible with the version of Serilog and other pre-existing libraries.

Replacing the already existing Serilog.*.dll files with different versions is sometimes possible but not recommended since it may lead to application instability and failures.

Configuration example

The example shows how to configure Serilog to write to a file, to the console and send errors to an email address.

Since Serilog.Sinks.Email is not included in the release, it needs to be supplied manually, including all its dependencies:

• Serilog.Sinks.Email
• Serilog.Sinks.PeriodicBatching (dependency of Serilog.Sinks.Email)
• Mailkit (dependency of Serilog.Sinks.Email)

logging.json

{
  "Serilog": {
    "Using": [
      "Serilog.Sinks.Console",
      "Serilog.Sinks.File",
      "Serilog.Sinks.Email"
    ],
    "MinimumLevel": "Information",
    "WriteTo": [
      {
        "Name": "Console"
      },
      {
        "Name": "File",
        "Args": {
          "path": "D:\\logs\\buru.log",
          "restrictedToMinimumLevel": "Warning"
        }
      },
      {
        "Name": "Email",
        "Args": {
          "restrictedToMinimumLevel": "Error",
          "fromEmail": "mail@rebex.net",
          "toEmail": "mail@rebex.net",
          "mailServer": "smtp"
        }
      }
    ]
  }
}

config.yaml

logging:
  useCustomConfig: true

Included libraries and their nuget versions

Notes

Access logs are distinguished by Access Serilog property.