Appearance
Streams & Keys
A Stream holds one kind of telemetry. An ingest key grants write access to one Stream. Both live under Telemetry → Manage Streams in the Console.
Streams
Click + New Stream, pick a type, then set a name and a retention.
- The type decides which data the Stream accepts (below).
- The retention is 7, 15, 30, 60 or 90 days, up to the plan's maximum. Older data is deleted automatically. Retention changes take effect immediately: a shorter retention hides older data right away.
Stream types
| Type | Holds | Send with |
|---|---|---|
| Events | Website analytics, product events and simple logs | JSON over the HTTP API, or the Analytics script |
| OpenTelemetry | Logs, traces and metrics | Any OpenTelemetry SDK or Collector |
An OpenTelemetry Stream takes all three signals through one endpoint with one key, and the console shows each under Logs, Traces and Metrics. Most apps need one Events Stream for the website and one OpenTelemetry Stream per service or environment.
Ingest keys
Select a Stream, open Keys & Setup and click Issue Key. Keys look like lit_XXXXXXXXXXX. The list shows each key as a preview; Reveal shows the full key and Copy copies the key, any time. Only members who can edit the namespace can reveal keys, and every reveal is recorded in the audit log.
A key writes to exactly one Stream and nothing else: the key decides where data goes, so requests don't name a Stream. Keys can't read data or touch the account, which makes keys safe for browser code.
Each key shows a state and when the key was last used:
| State | Meaning |
|---|---|
| Active | Accepted |
| Disabled | Paused: requests get 401 until Enable |
| Revoked | Permanently rejected |
Disable is the quick way to stop a misbehaving sender without losing the key. Revoke can't be undone.
Rotating a key
A Stream can hold several keys at once, so rotation needs no downtime:
- Click Issue Key to create the new key.
- Deploy the new key.
- Click Revoke on the old key once everything is using the new one.
Disabling, enabling and revoking all take effect within seconds, everywhere.
Key limits
Limits on a key caps requests or data per minute below the plan budget. Useful for keys that can't stay secret, like one in browser code: a leaked key can send at most the limit. Over the limit, requests with that key get 429, and every other key carries on. See Rate limits.
Usage and ingest health
Selecting a Stream in Manage Streams opens the Stream Overview:
- Live status: whether data is arriving right now, and how fast.
- Usage this month and in the last 24 hours: events, data received, and records rejected, dropped, throttled or sampled out, next to the account's monthly events.
- Ingest health: every reason data was rejected, dropped, throttled or set aside in the last 7 days, with a count and an example. Find dropped records searches for them in Explore.
- Limits that apply to the Stream, and Stream settings.
When we block a key or Stream (for abuse, or a runaway sender), the Overview says so and why, and senders get 403 ingest_blocked.
Deleting a Stream
Click Delete Stream. The Stream stops accepting data immediately (senders get 401s) and moves to Deleted Streams at the bottom of the list, with two options:
- Restore, keys and data included.
- Delete Permanently, which erases the Stream's data, keys and alerts. This can't be undone.
Who can manage Streams
Anyone with write access to the namespace can create and delete Streams and issue, disable or revoke keys. Read-only members can still explore the data and see each Stream's Overview.