Nats Exporter
Supported Telemetry
Overview
Exports traces, metrics, and logs to a NATS server. Payloads are published to NATS subjects using core NATS (fire-and-forget) or, optionally, JetStream for durable, acknowledged delivery.[!NOTE] This component is in development. The configuration surface described below is stable, but the publishing implementation is being contributed incrementally.
Configuration
Signal configuration
Each oflogs, metrics, and traces accepts:
JetStream
When thejetstream block is present, every payload is published with JetStream
and the publish blocks until the server acknowledges persistence.
By default the exporter ensures a stream exists for the configured subjects,
creating one with lightweight defaults if it is absent: a single stream, limits
retention bounded by both max_age and max_bytes, file storage, and a single
replica. These defaults are sized for a small or edge deployment and are safe to
run on a single-node server; scale them up (notably to three replicas) for a
clustered hub. Set stream.manage: false to require a pre-existing stream
instead — appropriate when the exporter holds publish-only credentials or streams
are provisioned externally.
Sharding a high-volume signal across multiple streams is a planned scale-up
option and is not yet configurable.
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-10-05