NATS
NATS Integration enables Belden Horizon Data Operations to connect to a NATS server.
Supported communication
- Outbound (Publish data from Edge to NATS server) - Yes
- Inbound (Subscribe data from NATS server to Edge) - Yes
Configurations
Field | Details | Required |
|---|---|---|
Name | Name of the connector instance. | Yes |
Hostname | Hostname of the NATS server. | Yes |
Port | Port of NATS host. | Yes |
NATS Username | Username for authenticating with the NATS server. Leave empty if the server does not require authentication. | No |
NATS Password | Password for authenticating with the NATS server. Leave empty if the server does not require authentication. | No |
Default topic name | Default NATS subject messages are published to when no subject override is provided by the data pipeline. | Yes |
Parallel Publish Count | Number of messages published in parallel. Higher values increase throughput and resource usage. | Yes |
Enable TLS secure connection | Encrypt the connection to the NATS server using TLS. Requires a valid server certificate. Use Insecure skip verify to bypass certificate validation during testing. | Yes |
Insecure skip verify | InsecureSkipVerify controls whether a client verifies the server's certificate chain and host name. | No |
Max Reconnect | Sets the number of reconnect attempts that will be tried before giving up. If negative, it will never give up trying to reconnect. | No |
Reconnect wait (second) | ReconnectWait sets the time to backoff after attempting a reconnect to a server that we were already connected to previously. | No |
Connect timeout (second) | Timeout sets the timeout for a Dial operation on a connection. | No |
Flush timeout (second) | Timeout for flushing buffered messages to the server during publish operations. | No |
Throttling limit | Set a limit on the number of outbound messages per second. If sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost. | No |
Persistent storage configurations
Field | Details | Required |
|---|---|---|
Persistent storage | If enabled, messages in the outbound queue are stored on disk. If there are interruptions in connection or power loss, messages are retained and eventually sent when the connection is restored. | No |
Persistent storage size limit | Set the size limit for storing persisted data in GB. | No |
Queue mode | Select the sequence of data transfer: FIFO or LIFO. Selecting FIFO (First In First Out) sends the earliest message first. Selecting LIFO (Last In First Out) sends the latest message first. | No |