descriptionLogs

Logs

Every log you send Zharp — from your servers, your hosting provider, your code or the API — lands in one place, where you can search it, follow it live and alert on it.

Where logs come from

Pick whichever fits; most workspaces use more than one, and they all end up on the same Logs page.

You have	Use	Key
A server, VM or Kubernetes cluster	The Zharp agent — Docker, systemd, PM2, nginx and log files, found by itself	None: the install command carries it
An app on Vercel, Render, Heroku, Fly.io, Cloudflare, AWS…	A log source — the platform drains its logs to Zharp	None: each source has its own token
Code you want to log from directly	A Zharp SDK, with tracing off if you only want logs	An app's key
Anything that can make an HTTP request	The HTTP API — POST a JSON list of lines	A workspace key with Ingest only

Each line is filed under a service name, and can carry an environment, a version and a source — see Tags & parsing. Lines from an app instrumented with a Zharp SDK or OpenTelemetry also appear on that app's Logs tab in App Telemetry, where each one opens its trace, user and session.

The Logs page

Logs in the sidebar opens on your services: one row each, with the last hour as a sparkline (errors in red), lines per minute, error rate and when it last logged. Switch between list and grid at the top. A service with no lines in the last hour is greyed; one with a high error rate is red.

A service's stream

Click a service to open its lines. From there:

LIVE follows new lines as they arrive; click it to pause and resume. 1H and 24H show a fixed window instead.
The services menu switches to another service, or All Services.
LEVELS narrows to one level: error, warn, info, debug, trace or fatal.
The search box matches words in the message, and @field conditions match what Zharp parsed from the line — @http.status_code>=500, @client.ip=10.0.0.4. See Parsed formats.

Alerts on logs

A log monitor watches one or more services and opens an incident as soon as a line matches one of your patterns. It alerts like any other monitor.

Retention

Logs are kept for 7 days on Free, 30 on Pro and 90 on Business, and each plan has a monthly allowance. Lines you don't need can be dropped on arrival so they don't count — see Drop rules & retention.

terminal

From your servers

Install the agent; containers, services and files are picked up by themselves.

cloud

From hosting providers

Point Vercel, Render, Heroku and others at Zharp.

code

From your code

Log from your app with a Zharp SDK, logs only.

send

HTTP API

Send lines from anything that can make a request.