Streams

A stream is the destination used to organize logs inside one account. A receiver routes accepted events to its configured stream.

Create a stream

Open Streams, choose Create stream, give it a clear name, and save it. Useful boundaries include application, environment, or team ownership.

Keep the number of streams practical. Use structured fields and labels when a filter is enough; use a separate stream when the logs need a different receiver route or operational boundary.

Route a receiver

Choose the stream while creating or editing a receiver. Once the receiver is active, new accepted events go to that stream.

Sender fields such as stream_id, host, GELF host, or Fluent tag cannot select another account or bypass the configured route.

Verify

Send a known event through the receiver, open the stream in Live Tail, and search for its message. If it appears in another stream, inspect the receiver’s configured destination.

Retire safely

Check which receivers use a stream before removing it. Hosted MCP mutations use a proposal and a short-lived confirmation token before applying a change.

Next: Create a receiver or read logs in Live Tail.