Skip to content

Connects to a remote TCP or TLS endpoint and receives events.

from_tcp endpoint:string, [tls=record, {}]

Connects to the specified TCP endpoint as a client and reads bytes from the connection, running them through an optional nested pipeline.

If the connection fails, the operator retries with exponential backoff.

The remote endpoint to connect to. Must be of the form [tcp://]<hostname>:<port>.

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.

The pipeline to run for the TCP connection. Use this to parse the incoming byte stream into events, for instance { read_json }.

Inside the pipeline, the $peer variable is available as a record with the following fields:

FieldTypeDescription
ipipThe IP address of the remote peer
portint64The port number of the remote peer
from_tcp "example.org:4000" {
read_json
}
from_tcp "example.org:4443", tls={} {
read_json
}

Connect with TLS and a custom CA certificate

Section titled “Connect with TLS and a custom CA certificate”
from_tcp "example.org:4443", tls={cacert: "ca.pem"} {
read_json
}

Last updated: