One platform for collecting, searching, understanding, and acting on your logs — with the two features nobody else has: git regression detection and zip-the-diff patterns.
When an error carries a stack trace, ZipLogger goes further than any log tool you've used:
it parses every file:line frame, runs git blame against the repositories you've
connected, and produces a ranked list of suspect commits — weighted by how recently they touched
the exact lines that are now failing.
With AI enabled, each regression case gets a written root-cause analysis and a suggested fix, ready to paste into your incident channel.
# Regression case #42 — checkout NullReference
Suspects (ranked):
1. a3f92c1 refactor currency handling
dana@acme · 2h before first error · score 0.91
2. 88d01ce bump payment SDK to 4.2
lee@acme · 2d before · score 0.34
AI: `Currency` can be null when the cart was
created before the deploy. Guard in
PaymentProcessor.Charge() or backfill carts.Two AI features, both practical. Summarize errors turns any time window into a short root-cause narrative: what broke, where, how often, since when. Ask converts plain English into real queries — “warnings from the API since last night” just works.
"why are checkout errors spiking?"
→ severity:error source:checkout, last 2h
Summary: 214 NullReference errors from
PaymentProcessor.Charge(), starting 14:10 —
right after release 2.4.1. Affects ~3% of
checkouts. One pattern, one suspect commit.ZipLogger's pattern engine groups similar messages into templates in real time. Instead of scrolling 400,000 lines, you read ten patterns — each showing its count, trend, and exactly which parts vary between occurrences. It's compression for your attention.
142,801 Order <*> created — <*> items, $<*>
98,112 GET /api/<*> completed in <*> ms
214 Payment failed: <*> — Charge() ⚠
12 Retry <*>/3 for order #<*>Every service, container, and job logs to one place — and search stays fast as your volume grows, with retention managed automatically by your plan. Full-text, field filters, time ranges, histograms — everything composes.
severity:error source:checkout release:2.4.1
→ 214 events in 38 ms
fields.orderId:83112
→ the full story of one order, all servicesCompose timeseries, stat, and top-values panels from any query. Watch error rates, top sources, and release health on one screen — saved per team, no extra product to buy.
Threshold rules on any query, evaluated continuously by a background engine. Slack and webhook delivery, flap-resistant state tracking, and a full history of every firing.
Fields, tags, releases, commit SHAs, machine and environment — captured automatically by the SDKs, stored as first-class data, and searchable without any parsing rules.
A native OTLP/HTTP logs receiver accepting protobuf and JSON (gzip included), with resource attributes mapped to first-class fields. Point your existing exporter at ZipLogger and go.
.NET (ILogger, Serilog), Python, Node.js (Pino, Winston), Go (slog), Java, and the browser — all dependency-free, all with the same batching, retry, backpressure, and enrichment behavior.
Everything the UI does, the API does: NDJSON ingestion, search, dashboards, alerts, billing, usage. Per-tenant API keys with one-way hashing and instant revocation.
Multi-tenant from the ground up with Admin, Editor, and Viewer roles, per-tenant isolation down complete separation between workspaces, and audit logs of every destructive action on Team plans and above.
JWT auth with refresh-token rotation, hashed API keys, role-based authorization, tenant isolation, audit trails — and because it's self-hosted, your logs never leave your network.
Ingestion never blocks or slows your applications, even under burst load — and search stays fast whether you keep thousands of events or billions. Performance you never have to think about.
The free plan includes search, patterns, dashboards, and alerts — no card required. Trials of Developer and above unlock AI analysis and git regression detection.