Connect-specific parameters

The connect key sets parameters that are specific to OMEGAMON® Data Connect.

connect:
  input:
    tcp: # Required
      <TCP input parameters>

  output: # At least one output is required
    tcp:
      <TCP output parameters>

    http:
      <HTTP output parameters>

    otel: # Experimental
      <OpenTelemetry output parameters>

    kafka:
      <Kafka output parameters>

    prometheus:
      <Prometheus output parameters>

    stdout:
      <STDOUT output parameters>

  filter: # Optional
    <Global-level filter for JSON outputs>

  event-publisher: # Optional
    <Event publisher parameters>

  logging: # Optional
    <Connect-specific logging parameters>
input
OMEGAMON Data Connect supports a single input: data from OMEGAMON Data Broker over TCP.
output
A single instance of OMEGAMON Data Connect can send data to all of these outputs:
tcp
JSON Lines over TCP. You can specify multiple destinations (sinks) for TCP output.
http
JSON in HTTP POST requests. You can specify multiple destinations (endpoints) for HTTP output.
otel
Experimental: OpenTelemetry (OTel) Protocol over gRPC (OTLP/gRPC). You can specify multiple destinations (endpoints) for OpenTelemetry output.
kafka
JSON published to Apache Kafka. You can publish either to a single topic, or to a separate topic for each table (for example, each OMEGAMON attribute group).
prometheus
Prometheus metrics HTTP endpoint hosted by OMEGAMON Data Connect.
stdout
JSON Lines written to the stdout file.
filter
Filters which tables (such as OMEGAMON attribute groups) and which fields (such as OMEGAMON attributes) from those tables to send to the JSON-format outputs: tcp, http, kafka, and stdout.
event-publisher
Controls aspects of internal OMEGAMON Data Connect processing.
logging
Controls logging behavior specific to OMEGAMON Data Connect, such as flood control.