VitePress

Appearance

Telemetry ​

Beta

Telemetry is in beta. It's included with paid plans at no extra cost while in beta, and limits are subject to change. See Limits & Errors for what each plan includes.

Your monitors tell you that something broke. Telemetry tells you why. Send your app's logs, traces, metrics and events to Latency and explore them in the same console as your monitors and incidents.

How it works ​

  1. Create a Stream. A Stream is a named home for one kind of data, with its own retention.
  2. Issue an ingest key. Each key writes to one Stream and nothing else, so the key alone decides where data goes.
  3. Send data. Point an OpenTelemetry SDK at Latency, or POST JSON from anything that can make an HTTP request.

Data shows up under Telemetry in the Console, usually within a couple of seconds. A live indicator next to the Stream picker shows when data is arriving.

Two ways to send ​

Best for
OpenTelemetryApps and services. Automatic traces, metrics and logs from the standard SDK in every major language.
HTTP APIScripts, cron jobs, browsers, webhooks: anything without an SDK.

Not sure? Start with OpenTelemetry. It's the industry standard, so nothing you add ties you to Latency.

What you can send ​

SignalWhat it answersExample
LogsWhat did my code say?payment failed for order o-9
TracesWhere did the time go?one checkout request, span by span, across services
MetricsHow is it trending?requests per second, p99 latency, queue depth
EventsWhat happened?pageviews, signups, deploys

Delivery you can count on ​

When Latency answers 202 Accepted (or 200 for OpenTelemetry), your data is already replicated across regions. It's written to storage in the background, and if storage is slow it waits in that buffer instead of being dropped.

If we can't take a request, you get a 429 or 503 with a Retry-After header. OpenTelemetry SDKs retry those on their own. See Limits & Errors.

Next steps ​

© 2026 Latency Labs LLC