Official SDKs for six platforms, a native OpenTelemetry receiver, and a plain HTTP API mean almost anything can log to ZipLogger today — and the list keeps growing.
First-class support via the ZipLogger.Client core package: batching, retries,
backpressure, and automatic release/commit enrichment.
Two lines in Program.cs. Request logs, scopes, and unhandled exceptions flow
automatically through the standard logging pipeline.
.WriteTo.ZipLogger(endpoint, apiKey) — structured properties, destructured
objects, and exceptions preserved as searchable fields.
builder.Logging.AddZipLogger(...) — an ILoggerProvider with scopes,
config-file binding, and per-category level filtering.
A dependency-free logging handler: pip install ziplogger, add
ZipLoggerHandler, and extra= values become searchable fields —
tracebacks feed regression detection.
npm install ziplogger — a zero-dependency core client plus first-class
Pino and Winston transports with the same batching and retry semantics as
the .NET packages.
go get a standard-library-only client with a first-class log/slog
handler — attributes become searchable fields, err attrs feed regression
detection.
A JDK-only client (Java 17+) with a java.util.logging handler. Zero dependencies,
same batching and retry semantics as every other SDK.
@ziplogger/browser captures uncaught errors and unhandled rejections, flushes
on page unload, and ships a React error boundary with component stacks.
Native OTLP/HTTP logs receiver (protobuf + JSON, gzip). Point
OTEL_EXPORTER_OTLP_ENDPOINT at ZipLogger — resource attributes, trace IDs, and
exceptions map to first-class fields.
Use the otlphttp exporter to fan logs from any language or agent into ZipLogger —
the door to Python, Node.js, Java, and Go today.
One authenticated endpoint accepts a single event, a JSON array, or NDJSON streams. If it can POST JSON, it can log to ZipLogger — cron jobs, shell scripts, legacy apps.
Alert notifications deliver to Slack incoming webhooks or any HTTP endpoint — wire firing alerts into PagerDuty, Teams, or your own automation.
ZipLogger installs on a single modest server in about ten minutes — AWS, Azure, GCP, a VPS, or the machine in your rack. No specialist knowledge required.
Self-hosted means exactly that: logs, metrics, and search stay on infrastructure you control. Ideal for regulated industries and privacy-sensitive teams.
The same installation serves a side project and a production fleet logging millions of events a day — search stays fast, and nothing needs re-architecting as you scale.
Tail files and containers from apps you can't modify — the http output ships
NDJSON straight to ZipLogger. Copy-paste pipeline →
High-performance pipelines with remapping: rename keys, set severities, and stream to the ingestion endpoint. Copy-paste pipeline →
Filebeat, syslog relays, custom scripts — if it can POST newline-delimited JSON with a header, it can feed ZipLogger.
Native Logger/Monolog integrations. Today: the OTel Collector or HTTP API route works for both.
Query ZipLogger from dashboards you already have. Today: the REST API covers custom panels.
Native alert routing. Today: both accept ZipLogger's webhook notifications via their APIs.
Tell us what your stack looks like — integrations are prioritized by real demand.