Parse log lines into fields and metrics
Add fields to plain-text logs as they arrive with pattern, JSON or key=value rules, then turn matching logs into a metric you can chart and alert on.
Blog
Guides for finding out what broke
How to send logs and traces, trace an error back to the commit that caused it, and keep an eye on the parts of your system that fail quietly. Real code, from the SDKs we ship.
Sending logs and traces
Centralized .NET logging with Serilog and ILogger
Send ASP.NET Core logs to ZipLogger with the Serilog sink or the ILogger provider, with structured properties you can search by user or order id.
Centralized Go logging with slog and ZipLogger
A log/slog handler that sends Go logs to the cloud. The real module path, how attributes become fields, errors, and what Close does.
Centralized Java logging with ZipLogger
Send Java logs to the cloud with the ZipLogger java.util.logging handler or its client. Maven and Gradle setup, fields, stack traces, shutdown.
Centralized Node.js logging with ZipLogger
Send Node.js logs to the cloud through Pino, Winston or a plain client. Setup, the JSON each line becomes, errors, and flushing on shutdown.
Centralized Python logging with ZipLogger
Send Python logs to the cloud with the standard logging module and one handler. Setup, Django config, searchable extra fields and tracebacks.
Send logs over HTTP with curl
Send logs from shell scripts, CI jobs or any language with one HTTP POST. Real curl samples, body formats, severity rules, limits and responses.
Send OpenTelemetry traces over OTLP/HTTP
Point any OpenTelemetry SDK or Collector at ZipLogger over OTLP/HTTP. The exact endpoints, the auth header, .NET and Node.js setups, and what is not supported.
Ship logs with Fluent Bit or Vector
Send log files and Docker or Kubernetes container output to ZipLogger with Fluent Bit's http output or Vector's http sink. Configs and field rules.
Trace a click from the browser to the backend
Send a W3C traceparent header from the browser so your backend's OpenTelemetry spans join the same trace. CORS setup and real output included.
Finding the cause
Create GitHub, Jira or Linear issues from errors
Open a GitHub, Jira Cloud or Linear issue from a ZipLogger Issue, or link one you have. What gets sent, what never does, setup per tracker, and the limits.
Release health: crash-free sessions per release
See crash-free sessions, crash-free users and adoption for each release, from Sentry SDKs or ZipLogger's own SDKs, and get alerted when a release crashes more.
Use the Sentry SDK with ZipLogger
Keep your Sentry SDK and send its errors, traces and logs to ZipLogger by changing the DSN. Node, browser and Python setups, and what is dropped.
AI log analysis with your own API key
How ZipLogger's AI analysis works with your own Anthropic, OpenAI or Gemini key: what each feature does, exactly what is sent to the model, and the limits.
Find the commit that broke production
How to trace a production error back to the commit that caused it, from stack trace to git blame to a short list of suspects, and how ZipLogger does it for you.
Follow one error across logs, traces and events
Correlate logs, traces and product events by trace id and session id on ZipLogger's Investigate page, and what your apps must send for the join to work.
JavaScript and React error tracking
Catch uncaught JavaScript errors, promise rejections and React render errors with @ziplogger/browser. Real payloads, plus what it does not do.
Log pattern clustering, explained with real output
How Drain-style log pattern detection groups similar log messages into templates, where it gets things wrong, and how to use patterns in ZipLogger.
Query and export logs over HTTP
Read logs out of ZipLogger from a script or CI job: the REST search API with cursor paging, the read-key Loki endpoint, real requests and their limits.
Query production logs from Claude Code or Cursor
Connect Claude Code, Cursor or any MCP client to ZipLogger's MCP server so your AI assistant can read logs, error patterns, traces and git regressions.
Query ZipLogger from Grafana, no plugin
Point Grafana's built-in Loki, Prometheus and Tempo data sources at ZipLogger. The real URLs, auth, and exactly which LogQL and PromQL queries work.
Monitoring and alerts
Kubernetes monitoring with one Helm chart
Install one read-only Helm chart per cluster and see nodes, workloads, pods and events, plus crash loops, image pull errors and missing Secrets as incidents.
Metric monitors and anomaly alerts
Alert when any metric crosses a line or looks unusual for the time of day, with CPU per host from the OpenTelemetry Collector as a worked example.
SLOs and burn-rate alerts for your services
Set an availability or latency SLO on a service or endpoint in ZipLogger APM, watch the error budget, and page only when it burns fast.
Uptime monitoring: HTTP, TCP, DNS and ping checks
Check a URL, a page's text, a port, a DNS record or a ping on a schedule, page on-call only when locations agree, and get warned before a certificate or domain expires.
Alert on error logs and quiet services
Set up log-based alert rules that fire on error spikes or when a service goes quiet, send them to email or Slack, and keep them from paging for nothing.
ASP.NET Core request metrics: p95 and throughput
Time every ASP.NET Core request with one NuGet package and see average latency, p95 and throughput per service. Real payloads, config, and limits.
Build an error rate dashboard in ZipLogger
Put error rate, top errors, active alerts, service health and the last deploy on one screen. Widgets, variables, filters, sharing and JSON export explained.
Cron job monitoring: alert when a job doesn't run
Use a heartbeat to find out when a cron job stops running, fails or hangs: a plain ping URL, cron schedules with time zones, Sentry check-ins, and curl and .NET samples.
Synthetic monitoring: replay a real user journey
Record a sign-in or checkout once in a real browser, replay it on a schedule in Chromium, and get the failing step with a screenshot, console errors and failed requests.
Incident response
Discord and Telegram incident alerts
Post ZipLogger incidents to a Discord channel or a Telegram chat as one message that is edited as the incident is acknowledged and resolved. Setup, payloads and limits.
Publish a status page for your customers
Give customers one page that shows whether your service works, with components driven by monitors, incidents, maintenance and email, Slack, webhook or SMS updates.
Microsoft Teams incident alerts with actions
Get ZipLogger incident cards in a Teams channel or chat, and acknowledge, assign or resolve them from the card. Setup, account linking and limits.
On-call schedules and escalation policies
Set up on-call teams, rotations with primary and secondary layers, overrides, a repeating escalation policy, calendar subscriptions and postmortems in ZipLogger.
Route CloudWatch and Datadog alerts to on-call
Send CloudWatch, Datadog, Alertmanager and other alerts into ZipLogger incidents by webhook, with dedup, auto-resolve and optional hand-off to PagerDuty.
Slack incident alerts you can acknowledge
Post ZipLogger incidents to a Slack channel as one message that updates in place, with Acknowledge, Assign to me and Resolve buttons that act as the person who clicked.
SMS and voice call paging for incidents
Page on-call engineers by SMS and phone call in ZipLogger, and let them acknowledge by replying or pressing 1. Built-in sender or your own Twilio or Telnyx.
Product analytics and replay
Funnel drop-off: who left and what they did next
Build a saved checkout process in ZipLogger, open the exact people who dropped at a step, and see the next thing each of them did. Limits included.
Cohort retention: how the numbers are counted
What a ZipLogger retention chart counts, cell by cell: who enters a cohort, what counts as coming back, calendar buckets, and how saved cohorts narrow it.
Funnel analysis: sequential vs presence funnels
Build a conversion funnel from tracked events, see why sequential and presence modes give different numbers, and trace a drop-off to the errors behind it.
Identify anonymous users and follow their journey
Link a visitor's anonymous events to their account with identify(), then read their profile and session timeline with the errors and replay beside it.
Move off Mixpanel without rewriting tracking
Point mixpanel-browser or the Mixpanel Node library at ZipLogger with one host setting. What carries over, what does not, and the native alternative.
Session replay without recording passwords
How ZipLogger's session replay masks passwords, card fields and typed input in the browser before upload, and how to mask or block anything else.
Workspaces and access
Enterprise SSO with Microsoft Entra ID
Connect a ZipLogger workspace to Microsoft Entra ID, test it, require it for everyone, keep recovery codes, and know what enforcement does not reach.
Separate staging and production logs
Keep Staging and Development telemetry apart from Production inside one ZipLogger workspace, with one ingest key per environment and alert rules that only count their own data.
White label logging for agencies and MSPs
Put a client's name, logo, favicon and colours on their ZipLogger workspace, what white label removes on top of that, and what still says ZipLogger.
No posts match that. Try a shorter word, or look in the docs.
Try it on your own logs
There is a free plan and no sales call. Install an SDK, send a few log lines, and search them.