Receivers
A receiver owns one protocol and one route into a stream.
Prerequisites
Section titled “Prerequisites”Create the destination stream first. For a shared receiver, be ready to create and store a receiver-bound token. For a dedicated receiver, know the sender’s public IPv4 address or CIDR and confirm that the account plan has a dedicated endpoint available.
Shared receivers
Section titled “Shared receivers”HTTP JSON, OTLP/HTTP, OTLP/gRPC, Prometheus text, and Prometheus remote_write share authenticated TLS port 443.
They have a stable receiver ID and require a token bound to that receiver. They do not consume a dedicated port. Wrong receiver, account, or token combinations are rejected before expensive payload parsing.
Dedicated receivers
Section titled “Dedicated receivers”Syslog, GELF, StatsD, Fluent Forward, and Beats use an assigned account destination. Configure the sender’s public IPv4 or CIDR and follow the transport and TLS rules shown by the receiver.
Dedicated endpoints count against the account’s configured limit. Fluxtail access and receiver limits are confirmed before setup. Do not configure a sender until the endpoint state is active.
Lifecycle
Section titled “Lifecycle”Retiring a dedicated receiver stops new use of its endpoint. Restoring is allowed only when the active plan limit permits it. A quarantined port is not reused for another receiver at launch.
Verify setup
Section titled “Verify setup”The receiver page is authoritative for:
- exact URL, hostname, and port;
- transport and TLS requirements;
- token or source-rule authentication;
- readiness and lifecycle state;
- current dedicated-port allowance.
Send one known event with the matching sender guide, then open the configured stream in Live Tail and search for its message.
Troubleshooting
Section titled “Troubleshooting”- Do not configure a dedicated sender until the endpoint state is
active. - For shared receivers, confirm the URL and token belong to the same receiver.
- For dedicated receivers, confirm the sender’s public IPv4 matches a source rule and the assigned port is allowed outbound.
- If the endpoint is healthy but no event appears, follow No logs appear.
Next steps
Section titled “Next steps”Use the receiver matrix to open the exact sender guide, or review access token safety before configuring a shared receiver.