Z8Log

At a glance

Z8Log collects structured JSON logs through HTTP and lets you query events, follow a flow ID and build charts. It is aimed at small applications that want a hosted view of what happened without adopting an SDK first. A dataset has its own access key and ingestion limit.

Good fit

Worth a small trial for a low-volume app where a few structured events would answer questions that console output cannot. A shared flow ID can connect the steps of one request or job. Start by checking whether the free plan’s sampling pace fits the events you actually need.

Consider something else when

You need high-volume telemetry or a safe public write-only browser key. The dataset bearer key can both ingest and query logs, so embedding it in public client code also exposes read access. Keep it behind a server boundary when the dataset is sensitive.

Start here

Start logging opens account creation. After signing up, create an isolated test dataset, send one synthetic INFO event with a flow ID using POST /api/logs/{id}, then query that flow before instrumenting real requests. Keep the dataset key private and avoid using the broader admin key in application code.

Cost and requirements

Free allows two datasets, one log per five seconds with a burst of three, and a three-day search window. Basic and Pro raise limits and extend the window to seven and thirty days; a public dollar price was not established. All plans cap message text at 1 KiB and serialized data at 2 KiB. Ingestion limits apply per dataset across its keys.

Limits to know

A search window is not a deletion promise: the documentation says older stored events can become visible after upgrading. Timeout retries can create duplicates, and throttling returns Retry-After. The privacy policy describes stored logs and account services but gives no fixed backup-erasure deadline. The account form was inspected; ingestion and dashboards were not exercised.

Still unclear

• What are the current dollar prices for Basic and Pro before committing to an account?