Skip to content
Written with Claude
IMPORTANT

As you may notice, this page and pretty much the entire website were obviously created with the help of AI. I wonder how you could tell? Was it a big "Written With Claude" badge on every page? I moved it to the top now (with the help of AI of course) to make it even more obvious. There are a few blogposts that were written by me manually, the old-fashioned way, I hope there will be more in the future, and those have a similar "Human Written" badge. This project (not the website), on the other hand, is a very, very different story. It took me more than two years of painstaking and unpaid work in my own free time. A story that, hopefully, I will tell someday. But meanwhile, what would you like me to do? To create a complex documentation website with a bunch of highly technical articles with the help of AI and fake it, to give you an illusion that I also did that manually? Like the half of itnernet is doing at this point? How does that makes any sense? Is that even fair to you? Or maybe to create this website manually, the old-fashioned way, just for you? While working a paid job for a salary, most of you wouldn't even get up in the morning. Would you like me to sing you a song while we're at it? For your personal entertainment? Seriously, get a grip. Do you find this information less valuable because of the way this website was created? I give my best to fix it to keep the information as accurate as possible, and I think it is very accurate at this point. If you find some mistakes, inaccurancies or problems, there is a comment section at the bottom of every page, which I also made with the help of the AI. And I woould very much appreciate if you leave your feedback there. Look, I'm just a guy who likes SQL, that's all. If you don't approve of how this website was constructed and the use of AI tools, I suggest closing this page and never wever coming back. And good riddance. And I would ban your access if I could know how. Thank you for your attention to this matter.

Logging

Logging configuration using Serilog for console, file, PostgreSQL database, and OpenTelemetry outputs.

Overview

json
{
  "Log": {
    "MinimalLevels": {
      "NpgsqlRest": "Information",
      "System": "Warning",
      "Microsoft": "Warning"
    },
    "ToConsole": true,
    "ConsoleMinimumLevel": "Verbose",
    "ToFile": false,
    "FilePath": "logs/log.txt",
    "FileSizeLimitBytes": 30000000,
    "FileMinimumLevel": "Verbose",
    "RetainedFileCountLimit": 30,
    "RollOnFileSizeLimit": true,
    "ToPostgres": false,
    "PostgresCommand": "call log($1,$2,$3,$4,$5)",
    "PostgresMinimumLevel": "Verbose",
    "ToOpenTelemetry": false,
    "OTLPEndpoint": "http://localhost:4317",
    "OTLPProtocol": "Grpc",
    "OTLPResourceAttributes": {
      "service.name": "{application}",
      "service.version": "1.0",
      "service.environment": "{environment}"
    },
    "OTLPHeaders": {},
    "OTLPMinimumLevel": "Verbose",
    "OutputTemplate": "[{Timestamp:HH:mm:ss.fff} {Level:u3}] {Message:lj} [{SourceContext}]{NewLine}{Exception}"
  }
}

Log Levels

Available log levels (from most to least verbose):

LevelDescription
VerboseMost detailed logging, typically for debugging
DebugDebugging information
InformationGeneral operational information
WarningWarnings that don't stop execution
ErrorErrors that affect specific operations
FatalCritical errors that stop the application

See Serilog Configuration Basics for more details.

Minimal Levels

Configure minimum log levels per source context:

json
{
  "Log": {
    "MinimalLevels": {
      "NpgsqlRest": "Information",
      "System": "Warning",
      "Microsoft": "Warning"
    }
  }
}
SettingTypeDefaultDescription
NpgsqlReststring"Information"Log level for NpgsqlRest operations. Uses the application logger named after ApplicationName.
Systemstring"Warning"Log level for .NET System namespace.
Microsoftstring"Warning"Log level for Microsoft namespace (ASP.NET Core, etc.).

Console Output

json
{
  "Log": {
    "ToConsole": true,
    "ConsoleMinimumLevel": "Verbose"
  }
}
SettingTypeDefaultDescription
ToConsolebooltrueEnable logging to console output.
ConsoleMinimumLevelstring"Verbose"Minimum log level for console output.

File Output

json
{
  "Log": {
    "ToFile": false,
    "FilePath": "logs/log.txt",
    "FileSizeLimitBytes": 30000000,
    "FileMinimumLevel": "Verbose",
    "RetainedFileCountLimit": 30,
    "RollOnFileSizeLimit": true
  }
}
SettingTypeDefaultDescription
ToFileboolfalseEnable logging to file system.
FilePathstring"logs/log.txt"File path for log files.
FileSizeLimitBytesint30000000Maximum size limit for log files in bytes before rolling (30 MB).
FileMinimumLevelstring"Verbose"Minimum log level for file output.
RetainedFileCountLimitint30Maximum number of log files to retain.
RollOnFileSizeLimitbooltrueCreate a new log file when size limit is reached.

PostgreSQL Output

json
{
  "Log": {
    "ToPostgres": false,
    "PostgresCommand": "call log($1,$2,$3,$4,$5)",
    "PostgresMinimumLevel": "Verbose"
  }
}
SettingTypeDefaultDescription
ToPostgresboolfalseEnable logging to PostgreSQL database.
PostgresCommandstring"call log($1,$2,$3,$4,$5)"PostgreSQL command to execute for database logging.
PostgresMinimumLevelstring"Verbose"Minimum log level for PostgreSQL output.

PostgreSQL Command Parameters

The PostgresCommand receives five parameters:

ParameterTypeDescription
$1textLog level (Verbose, Debug, Information, Warning, Error, Fatal)
$2textLog message
$3timestamptzTimestamp in UTC
$4textException text (or null if no exception)
$5textSource context (logger name)

OpenTelemetry Output

json
{
  "Log": {
    "ToOpenTelemetry": false,
    "OTLPEndpoint": "http://localhost:4317",
    "OTLPProtocol": "Grpc",
    "OTLPResourceAttributes": {
      "service.name": "{application}",
      "service.version": "1.0",
      "service.environment": "{environment}"
    },
    "OTLPHeaders": {},
    "OTLPMinimumLevel": "Verbose"
  }
}
SettingTypeDefaultDescription
ToOpenTelemetryboolfalseEnable OpenTelemetry protocol (OTLP) logging output.
OTLPEndpointstring"http://localhost:4317"OTLP collector endpoint URL.
OTLPProtocolstring"Grpc"Protocol for OTLP: "Grpc" or "HttpProtobuf".
OTLPResourceAttributesobject(see below)Resource attributes sent with logs.
OTLPHeadersobject{}Custom headers for OTLP requests.
OTLPMinimumLevelstring"Verbose"Minimum log level for OTLP output.

Resource Attributes

Default resource attributes use placeholders:

AttributeDefaultDescription
service.name"{application}"Application name from ApplicationName setting.
service.version"1.0"Application version.
service.environment"{environment}"Environment name from EnvironmentName setting.

Output Template

json
{
  "Log": {
    "OutputTemplate": "[{Timestamp:HH:mm:ss.fff} {Level:u3}] {Message:lj} [{SourceContext}]{NewLine}{Exception}"
  }
}
SettingTypeDefaultDescription
OutputTemplatestring"[{Timestamp:HH:mm:ss.fff} {Level:u3}] {Message:lj} [{SourceContext}]{NewLine}{Exception}"Serilog output template for formatting log messages.

See Serilog Formatting Output for template syntax.

Complete Example

Production configuration with file and PostgreSQL logging:

json
{
  "Log": {
    "MinimalLevels": {
      "NpgsqlRest": "Information",
      "System": "Warning",
      "Microsoft": "Warning"
    },
    "ToConsole": true,
    "ConsoleMinimumLevel": "Information",
    "ToFile": true,
    "FilePath": "/var/log/npgsqlrest/app.log",
    "FileSizeLimitBytes": 50000000,
    "FileMinimumLevel": "Information",
    "RetainedFileCountLimit": 14,
    "RollOnFileSizeLimit": true,
    "ToPostgres": true,
    "PostgresCommand": "call log($1,$2,$3,$4,$5)",
    "PostgresMinimumLevel": "Warning",
    "ToOpenTelemetry": false,
    "OutputTemplate": "[{Timestamp:yyyy-MM-dd HH:mm:ss.fff} {Level:u3}] {Message:lj} [{SourceContext}]{NewLine}{Exception}"
  }
}

Next Steps

Comments

Released under the MIT License.