Useful utilities for Microsoft.Extensions.Logging.
| Package | Description |
|---|---|
Invex.Extensions.Logging.File |
A simple, dependency-light file logger provider with size- and time-based rollover, disk usage caps, and per-level log file routing. |
Supported targets: net10.0, net9.0, net8.0, and netstandard2.0.
Install the package:
dotnet add package Invex.Extensions.Logging.FileRegister the provider:
using Invex.Extensions.Logging.File;
var builder = WebApplication.CreateBuilder(args);
builder.Logging.AddFile();That's it — log entries are now written to a Logs directory next to your application, in files named after
the application, rolled over daily or at 100 MiB (whichever comes first), with total disk usage capped at 10 GiB.
Log entries look like this:
[2026-06-11 09:41:23.123 +10:00 INF MyApp.Services.OrderService] Order 42 submitted
Configure via appsettings.json (the provider alias is File):
{
"Logging": {
"File": {
"LogDirectory": "Logs",
"LogName": "my-app",
"FileSizeLimitBytes": 104857600,
"RolloverInterval": "Day",
"MaxTotalSizeBytes": 10737418240,
"PerLevelLogName": {
"Error": "my-app-errors"
}
}
}
}Or in code:
builder.Logging.AddFile(options =>
{
options.LogDirectory = "Logs";
options.LogName = "my-app";
options.RolloverInterval = FileRolloverInterval.Hour;
});See the configuration guide for every option and its default.
By default, log entries are queued in memory and written to disk by a dedicated background thread, keeping file I/O off your application threads. If you need every entry persisted before the log call returns (for example, in short-lived tools where the process may exit abruptly), use direct mode:
builder.Logging.AddFile(buffered: false);See buffered vs. direct writing for details and trade-offs.
- Getting started
- Configuration
- File rollover and retention
- Buffered vs. direct writing
- Log output format
- API reference
Licensed under the terms of LICENSE.txt.