FluxtailCore concepts
Fluxtail receives logs, routes them into streams, stores them for the account’s retention period, and makes them available through the product, Stream API, and hosted MCP.
Account
Section titled “Account”An account owns its streams, receivers, sources, tokens, and logs. Every read and write is checked against one account. Membership roles are owner, admin, member, and viewer.
Stream
Section titled “Stream”A stream is a saved log destination. Receivers route accepted events to their configured stream. Use streams to separate applications, environments, or operational concerns without mixing account ownership.
Receiver
Section titled “Receiver”A receiver accepts one published wire protocol.
- Shared receivers use TLS port
443, an exact receiver URL or the OTLP gRPC service, and a receiver-bound Bearer token. - Dedicated receivers use an assigned account destination and source IPv4 or CIDR rules. Paid plan limits apply.
Dedicated endpoints are not ready until their state is active.
Access token
Section titled “Access token”An access token belongs to one account and has explicit scopes. Ingest tokens are bound to one shared receiver. Stream reads use logs:read or analytics:read and the active account header.
Each accepted record becomes a log event with a timestamp, message, severity, optional service and host fields, labels, and a public log ID. Fluxtail keeps sender metadata as data; it never treats fields such as host or stream ID as authentication.
Retention and usage
Section titled “Retention and usage”Retention begins when a log is stored. The plan effective at storage time owns the final retention period. Usage shown publicly is stored usage, not requests merely accepted into the queue.