Nats Receiver
Supported Telemetry
Overview
Receives traces, metrics, and logs from a NATS server. The receiver subscribes to NATS subjects using core NATS (at-most-once) or, optionally, consumes from a JetStream stream for durable, acknowledged delivery. This is the receive-side counterpart to the NATS exporter. With default settings, the two components use the same subjects and encoding.[!NOTE] This component is in development. The configuration surface described below is stable, but the receiving implementation is being contributed incrementally.
Delivery semantics
- Core NATS (default): at-most-once. There is no acknowledgement or
redelivery; a payload that fails to decode or that the pipeline rejects is
logged and dropped. Set
queue_groupto load balance a subject across several collector instances instead of each instance receiving every message. - JetStream (
jetstreamset): the receiver consumes from a stream and:- acks a message once the pipeline accepts it,
- naks it (triggering redelivery) when the pipeline returns an error,
- terminates it (no redelivery) when the payload cannot be decoded, so a malformed message is not redelivered forever.
Configuration
Signal configuration
Each oflogs, metrics, and traces accepts:
JetStream
[!NOTE] JetStream consumption is not yet implemented. The behavior described in this section is the planned design and is contributed in a follow-up.When the
jetstream block is present, each signal consumes from a JetStream
stream with explicit acknowledgement. The receiver does not create or manage
streams; a stream capturing the configured subject must already exist (for
example, one created by the NATS exporter).
Authentication
Authentication is configured under anauth: block. At most one authentication
method may be configured. See the NATS
authentication docs.
Example
Configuration
Example Configuration
Last generated: 2026-11-09