Receivers

A receiver owns one protocol and one route into a stream.

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

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 plan. Free accounts do not get a dedicated port. Do not configure a sender until the endpoint state is active.

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

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.

See the receiver matrix to choose a protocol.