RabbitMQ

Install

cargo install faucet-cli --features sink-rabbitmq
faucet init --sink rabbitmq

# Cargo.toml — use it as a library
cargo add faucet-sink-rabbitmq

Starter config

sink:
  type: rabbitmq
  config:
    # url: ""    # Full AMQP URI, e.g.
    # host: ""    # Broker host.
    # port: 0    # Broker port.
    # vhost: ""    # Virtual host.
    # auth: { type: none }    # one of: none, plain, external
      # --- Alternative variants — replace the block above with one of these ---
      # type: plain
      # config:
        # username: ""    # REQUIRED
        # password: ""    # REQUIRED
      #
      # type: external
    # tls: { ... }    # TLS (`amqps://`) settings.
    # connection_name: ""    # Client connection name shown in the RabbitMQ management UI.
    # heartbeat_secs: 0    # Requested heartbeat interval in seconds (`0` disables heartbeats).
    # connect_timeout_secs: 30    # Upper bound, in seconds, on establishing the connection (TCP + AMQP handshake, including any retries).
    # connect_retries: 0    # Extra TCP connect attempts (exponential backoff) before giving up.
    # exchange: ""    # Exchange to publish to.
    # exchange_kind: null    # When set, `exchange` is declared (durable) with this type before the first publish; otherwise it must already exist.
    # routing_key: ""    # Static routing key for every message.
    # routing_key_field: ""    # Top-level record field whose value (string, number or bool) is the routing key.
    # routing_key_jsonpath: ""    # JSONPath (e.g.
    # value_format: null    # How a message body maps to and from a JSON record.
    # persistent: true    # Publish with delivery mode 2 (persisted to disk on durable queues).
    # mandatory: true    # Publish with the `mandatory` flag: a message no queue is bound to receive is returned by the broker and surfaces as a per-row error (DLQ-routable) instead of being silently dropped.
    # publish_timeout_secs: 60    # Seconds one publish group (its publishes and their confirms) may take — a broker under a memory or disk alarm blocks publishers indefinitely.
    # confirm: true    # Enable publisher confirms: every batch waits for the broker to acknowledge each message before the write returns.
    # batch_size: 1000    # Messages published before waiting on their confirms.

Capabilities

Config fields