Skip to content

Publishes messages to a NATS JetStream subject.

to_nats subject:string, [message=blob|string, headers=record, url=secret,
tls=record, auth=record, _max_pending=int]

The to_nats operator publishes one NATS JetStream message per input event. The NATS server must have a JetStream stream that captures the target subject.

The operator uses the default URL nats://localhost:4222 unless you provide url or configure plugins.nats.url.

The NATS subject to publish to.

An expression that evaluates to the message payload for each row.

Defaults to the message field.

An expression that evaluates to a record of NATS headers for each row. Header values must be strings or lists of strings.

The NATS server URL.

If the URL has no scheme, Tenzir uses nats:// by default or tls:// when TLS is enabled. Use nats://, tls://, ws://, or wss:// to select a specific transport.

Authentication settings for the NATS connection. Each value can be a string or a secret.

Supported authentication records are:

  • {token: secret("NATS_TOKEN")} for token authentication.
  • {user: "alice", password: secret("NATS_PASSWORD")} for user/password authentication.
  • {credentials: "/path/to/user.creds"} for NATS credentials files.
  • {credentials: "/path/to/user.creds", seed: "/path/to/user.nk"} for credentials files with a separate seed file.
  • {credentials_memory: secret("NATS_CREDS")} for credentials content stored in a secret.

TLS configuration. Provide an empty record (tls={}) to enable TLS with defaults or set fields to customize it.

{
skip_peer_verification: bool, // skip certificate verification.
cacert: string, // CA bundle to verify peers.
certfile: string, // client certificate to present.
keyfile: string, // private key for the client certificate.
min_version: string, // minimum TLS version (`"1.0"`, `"1.1"`, `"1.2"`, "1.3"`).
ciphers: string, // OpenSSL cipher list string.
client_ca: string, // CA to validate client certificates.
require_client_cert, // require clients to present a certificate.
}

The client_ca and require_client_cert options are only applied for operators that accept incoming client connections, and otherwise ignored.

Any value not specified in the record will either be picked up from the configuration or if not configured will not be used by the operator.

See the Node TLS Setup guide for more details.

NATS uses the standard Tenzir tls record. The nats.c library does not expose a minimum TLS version setting, so tls.min_version is accepted for record compatibility but ignored with a warning.

from {
severity: "high",
message: "suspicious login",
}
to_nats "alerts", message=this.print_json()
from {
message: "hello",
headers: {
source: "tenzir",
tags: ["demo", "nats"],
},
}
to_nats "alerts", message=message, headers=headers
subscribe "alerts"
to_nats "alerts",
message=this.print_json(),
url="tls://nats.example.com:4222",
auth={token: secret("NATS_TOKEN")},
tls={}

Last updated: