Konso Logging .NET Client

The Konso Logging .NET Client Library simplifies capturing and centralizing logs from .NET applications. Logs are shipped to the Konso platform via your choice of transport.

Features

• Flexible transport: choose REST, gRPC, or their async (non-blocking) variants
• Plug-and-play: integrates with the standard
  ILogger<T>
  abstraction — no changes to your existing logging calls
• Centralized logs: search, filter, and analyze logs from all your services in one place
• Configurable log levels: ship only the severity you care about

Documentation

Konso API reference

Requirements

• .NET 10 or higher
• A Konso account with a created bucket (BucketId + API key)

Installation

NuGet\Install-Package Konso.Clients.Logs

Transport types

The async variants use an in-memory queue and a background

(

KonsoLogsProcessorService

) to drain it. They are recommended for latency-sensitive applications.

Getting Started

REST transport

Add to

:

Register in

:

gRPC transport

Add to

:

Register in

:

Async REST transport

Same configuration as REST, with

. The async transport requires the hosted services infrastructure — ensure your app calls

builder.Services.AddHostedService

or uses

WebApplication

/

IHost

which registers hosted services automatically.

Async gRPC transport

The

value drives which provider is used — no code changes needed when switching transports.

Inline configuration (alternative)

If you prefer not to use

, you can configure inline:

Correlation ID support (optional)

To automatically propagate correlation IDs from HTTP request headers or sessions, register

:

Logging usage

No changes needed to your existing code — use the standard

:

Support

For questions or issues please contact support@konso.io or open a GitHub issue.