ZipLogger.Client
0.6.0
dotnet add package ZipLogger.Client --version 0.6.0
NuGet\Install-Package ZipLogger.Client -Version 0.6.0
<PackageReference Include="ZipLogger.Client" Version="0.6.0" />
<PackageVersion Include="ZipLogger.Client" Version="0.6.0" />
<PackageReference Include="ZipLogger.Client" />
paket add ZipLogger.Client --version 0.6.0
#r "nuget: ZipLogger.Client, 0.6.0"
#:package ZipLogger.Client@0.6.0
#addin nuget:?package=ZipLogger.Client&version=0.6.0
#tool nuget:?package=ZipLogger.Client&version=0.6.0
ZipLogger.Client
Core transport for shipping logs to a ZipLogger server: bounded queue, NDJSON batching, retry with exponential backoff (429-aware), drop-on-backpressure, automatic enrichment (source, release, commit SHA, environment, machine name).
You usually don't reference this package directly. Use one of the adapters, which pull it in:
- ZipLogger.Extensions.Logging —
Microsoft.Extensions.Loggingprovider (builder.Logging.AddZipLogger(...)) - ZipLogger.Serilog —
Serilog sink (
.WriteTo.ZipLogger(...))
Reference it directly only to build a custom integration on top of ZipLoggerShipper /
ILogShipper, or to enqueue ClientLogEntry objects yourself:
await using var shipper = new ZipLoggerShipper(new ZipLoggerClientOptions
{
Endpoint = "https://app.ziplogger.ai",
ApiKey = "zk_...",
});
shipper.Enqueue(new ClientLogEntry { Message = "hello", Severity = "info" });
See the integration docs for all options and the OpenTelemetry (OTLP) alternative.
Need a ZipLogger server? Sign up free at ziplogger.ai — the free tier covers 1,000 logs/day. Full documentation: ziplogger.ai/docs.html
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- No dependencies.
-
net8.0
- No dependencies.
NuGet packages (2)
Showing the top 2 NuGet packages that depend on ZipLogger.Client:
| Package | Downloads |
|---|---|
|
ZipLogger.Serilog
Serilog sink for ZipLogger. Add with .WriteTo.ZipLogger(endpoint, apiKey) — structured properties, exceptions, and enrichment ship to your ZipLogger server in the background. Sign up free at https://ziplogger.ai. |
|
|
ZipLogger.Extensions.Logging
Microsoft.Extensions.Logging provider for ZipLogger. Add with builder.Logging.AddZipLogger(...) — structured logs, scopes, and exceptions ship to your ZipLogger server in the background. Sign up free at https://ziplogger.ai. Registers IEventTracker too, so Track()/Identify() for product-analytics events are injectable alongside logging, sharing one queue and connection. |
GitHub repositories
This package is not used by any popular GitHub repositories.
Product analytics: ZipLoggerShipper now also implements IEventTracker — Track("checkout_started", new { ... }) and Identify(userId, anonymousId) ship events to /ingest/v1/events on their own buffered channel (async, batched, retried, never throws). AmbientSession.Begin(...) stamps a session id on everything tracked in scope; events default their requestId from Activity.Current so they correlate with logs and traces. Existing logging APIs are unchanged.