Fluxtail

Start with one event

The fastest way to understand Fluxtail is to send one HTTP JSON event and watch it arrive in Live Tail. The quickstart uses the exact receiver URL copied from Fluxtail and a receiver-bound access token.

• First-log quickstartFrom a new receiver to a verified Live Tail event.Open →
• Core conceptsAccounts, receivers, streams, tokens, and retention.Read →
• No logs arriving?Work through authentication, routing, limits, and filters.Fix →

Choose the right path

Shared receivers use authenticated TLS on port 443. Dedicated receivers use an assigned hostname and port plus source IPv4 or CIDR rules.

• Receiver matrixCompare every published protocol, transport, and authentication rule.Compare →
• Ingest APIHTTP JSON, OTLP/HTTP, and Prometheus request contracts.Reference →
• Stream APIRead retained logs, histograms, and facets for one account.Reference →

Keep customer data private

Fluxtail data is isolated by account. Access tokens have explicit scopes. Hosted MCP uses OAuth and binds each connection to one account. Keep tokens in environment variables and never place them in tracked files.

• Access tokensChoose the smallest scopes and protect receiver credentials.Secure →
• Hosted MCPConnect compatible agents through OAuth with no local server.Connect →