ZipLogger.Extensions.Logging 0.6.0

ZipLogger.Extensions.Logging

Microsoft.Extensions.Logging provider for ZipLogger — log management and product analytics (search, events, dashboards, alerts, AI analysis, git regression attribution). Hosted at ziplogger.ai, or run your own.

Your application keeps logging through the standard ILogger abstraction; this provider ships entries to your ZipLogger server in the background.

Usage

builder.Logging.AddZipLogger(options =>
{
    options.Endpoint = "https://app.ziplogger.ai";
    options.ApiKey   = "zk_...";   // Settings → API keys in the ZipLogger UI
});

Product-analytics events

AddZipLogger also registers IEventTracker, so events are injectable anywhere — no second client to construct, and no second queue or connection: logging and events share one shipper.

public sealed class CheckoutService(IEventTracker analytics)
{
    public async Task PayAsync(Cart cart)
    {
        analytics.Track("checkout_started", new { amount = cart.Total }, userId: cart.UserId);
        // ...
    }
}

Identify(userId, anonymousId) links a visitor's pre-login events to their account. Both calls are fire-and-forget: they never block your request path and never throw.

Or from appsettings.json (call builder.Logging.AddZipLogger();):

{
  "Logging": {
    "ZipLogger": {
      "Endpoint": "https://app.ziplogger.ai",
      "ApiKey": "zk_...",
      "LogLevel": { "Default": "Information" }
    }
  }
}

Then log as usual — structured values, scopes, and exceptions all flow through:

logger.LogWarning("Payment {Status} for {Customer}", "declined", "acme");
logger.LogError(ex, "Sync failed");   // exception → stackTrace (feeds regression attribution)

Behavior

• Never blocks, never throws — bounded in-memory queue + background batching (NDJSON over HTTP).
• Drop over grow — under extreme backpressure entries are dropped and counted, memory stays bounded.
• Retry with exponential backoff + jitter, honoring 429 Retry-After.
• Automatic enrichment — source (assembly name), release (informational version), commit SHA (SourceLink suffix or GIT_COMMIT/COMMIT_SHA), environment, machine name.
• Graceful shutdown — buffered entries flush on dispose (bounded by ShutdownTimeout).

Prefer Serilog? Use ZipLogger.Serilog. Already on OpenTelemetry? ZipLogger also accepts OTLP/HTTP logs directly — see the integration docs.

Need a ZipLogger server? Sign up free at ziplogger.ai — the free tier covers 1,000 logs/day. Full documentation: ziplogger.ai/docs.html