LogBurrow.Abstractions 0.1.0

LogBurrow

High-performance, asynchronous .NET logging provider that offloads log delivery to RabbitMQ and stores them as structured documents in MongoDB. Minimizes application overhead and ensures reliable log ingestion.

How it works

your app  ──ILogger──▶  MessageBusLogger  ──LogEvent──▶  RabbitMQ (logs-queue)  ──▶  LogBurrow.Worker  ──▶  MongoDB

The producing application only references LogBurrow.Logging. It plugs a custom ILoggerProvider into the standard Microsoft.Extensions.Logging pipeline, so every ILogger call is turned into a LogEvent and published to the bus. If the broker is unreachable the event is written to the console instead, so nothing is silently dropped. A separate worker drains the queue and persists each entry into MongoDB (one collection per log level).

Projects

src/
  BuildingBlocks/
    Abstractions
    EventBus.RabbitMq
    Logging
    Persistence.Mongo
  Services/
    Worker
  LogBurrow.sln

Project and folder names carry no prefix; assemblies and namespaces stay under LogBurrow.* (e.g. Abstractions builds LogBurrow.Abstractions.dll).

Usage — producing application

builder.Logging
    .ClearProviders()
    .AddMessageBusLogging(
        connection: builder.Configuration.GetConfiguration<RabbitMqConnection>());

// optional: block startup until the logging bus is confirmed healthy
await app.AwaitLoggerMessageBus().RunAsync();

{
  "Logging": {
    "LogLevel": { "Default": "None" },
    "MessageBusLogging": {
      "LogLevel": { "Default": "Warning", "MassTransit": "Error" }
    }
  },
  "RabbitMqConnection": {
    "HostData": { "HostName": "localhost", "Port": 5672 },
    "VirtualHost": "/",
    "Credentials": { "Username": "guest", "Password": "guest" }
  }
}

MessageBusLogging is the provider alias — use it under Logging to control which levels this provider forwards, independently of the other providers.

Usage — running the sink

LogBurrow.Worker reads RabbitMqConnection and MongoDbConnection from configuration (see src/Services/Worker/appsettings.json) and can run as a container or a service.

dotnet run --project src/Services/Worker

Packages

The BuildingBlocks projects are published as NuGet packages (Services/Worker is not packable). Package ids keep the LogBurrow. prefix:

Consume

dotnet add package LogBurrow.Logging

Shared metadata and the single VersionPrefix live in src/Directory.Build.props.

Build & pack locally

dotnet build src/LogBurrow.sln

dotnet pack src/LogBurrow.sln -c Release -o artifacts

.nupkg + .snupkg land in artifacts/. To test against a consumer before publishing, add that folder as a source:

dotnet nuget add source "$(pwd)/artifacts" -n logburrow-local

Publish

CI mirrors the Telegram.Wallet.Pay.Dotnet layout:

Required repository secrets: NUGET_TOKEN (NuGet.org API key) and TOKEN (a PAT with repo scope, used to push the version tag). Control the bump with #patch / #minor / #major in a commit message; default is minor.

Manual push:

dotnet nuget push "artifacts/*.nupkg" --api-key <KEY> --source https://api.nuget.org/v3/index.json --skip-duplicate

Targets .NET 8.