Telemetry
Structured event ingestion

Turn application behavior into queryable event tables

Send pragmatic JSON events for product flows, APIs, jobs, webhooks, agents, and business operations. Telemetry creates and evolves the table schema so the data is ready for SQL.

Start freeRead the documentation

Outcomes

  • Keep event names and fields readable across services and coding agents.
  • Capture status, latency, identifiers, costs, and safe error context together.
  • Add fields as the workflow evolves without rebuilding a warehouse pipeline first.

How it works

A reviewable workflow from signal to decision

1

Choose one completed workflow

Start where a user, worker, API, webhook, or agent produces a meaningful outcome. A small event at the boundary is easier to trust than a giant payload.

2

Log the fields future questions need

Include stable identifiers, status, duration, environment, feature, and categorized error context. Keep secrets and raw private content out.

3

Verify the table before expanding

Send synthetic test events, inspect the inferred schema, and run the first query. Add more coverage only after the event contract is useful.

Capabilities

What is included

HTTP ingestion API plus JavaScript, Python, Go, and Rust SDKs
Nested JSON fields exposed as queryable dotted columns
Schema compatibility checks before events enter the live buffer
Automatic UTC timestamp field for time-series analysis
Read, write, and read-and-write API-key scopes

Documentation

Log API referenceSchema evolutionNaming event fields

See the analysis

SQL recipes that use this capability

Query Nested AI Tool-Call Events

Filter dotted nested fields and rank failing tools without flattening the original event payload.

Open recipe

Detect Missing Service Heartbeats

Find services, workers, or scheduled tasks that stopped reporting before a failure event appeared.

Open recipe

Calculate API Error Rate by Route

Use SQL to rank API routes by 5xx error rate while protecting the result from low-volume noise.

Open recipe

Start with one production workflow

Use a focused prompt, send synthetic events, and verify the first useful query before expanding coverage.

Open prompt pack