amqp_0_9
Sends messages to an AMQP (0.91) exchange. AMQP is a messaging protocol used by various message brokers, including RabbitMQ.
- Common
- Advanced
# Common config fields, showing default valuesoutput:label: ""amqp_0_9:urls: []exchange: benthos-exchangekey: benthos-keytype: ""metadata:exclude_prefixes: []max_in_flight: 1
# All config fields, showing default valuesoutput:label: ""amqp_0_9:urls: []exchange: benthos-exchangeexchange_declare:enabled: falsetype: directdurable: truekey: benthos-keytype: ""content_type: application/octet-streamcontent_encoding: ""metadata:exclude_prefixes: []priority: ""max_in_flight: 1persistent: falsemandatory: falseimmediate: falsetls:enabled: falseskip_cert_verify: falseenable_renegotiation: falseroot_cas: ""root_cas_file: ""client_certs: []
The metadata from each message are delivered as headers.
It's possible for this output type to create the target exchange by setting
exchange_declare.enabled
to true
, if the exchange already exists
then the declaration passively verifies that the settings match.
TLS is automatic when connecting to an amqps
URL, but custom
settings can be enabled in the tls
section.
The fields 'key' and 'type' can be dynamically set using function interpolations described here.
Performance​
This output benefits from sending multiple messages in flight in parallel for
improved performance. You can tune the max number of in flight messages with the
field max_in_flight
.
Fields​
urls
​
A list of URLs to connect to. The first URL to successfully establish a connection will be used until the connection is closed. If an item of the list contains commas it will be expanded into multiple URLs.
Type: array
Default: []
Requires version 3.58.0 or newer
# Examplesurls:- amqp://guest:guest@127.0.0.1:5672/urls:- amqp://127.0.0.1:5672/,amqp://127.0.0.2:5672/urls:- amqp://127.0.0.1:5672/- amqp://127.0.0.2:5672/
exchange
​
An AMQP exchange to publish to.
Type: string
Default: "benthos-exchange"
exchange_declare
​
Optionally declare the target exchange (passive).
Type: object
exchange_declare.enabled
​
Whether to declare the exchange.
Type: bool
Default: false
exchange_declare.type
​
The type of the exchange.
Type: string
Default: "direct"
Options: direct
, fanout
, topic
, x-custom
.
exchange_declare.durable
​
Whether the exchange should be durable.
Type: bool
Default: true
key
​
The binding key to set for each message. This field supports interpolation functions.
Type: string
Default: "benthos-key"
type
​
The type property to set for each message. This field supports interpolation functions.
Type: string
Default: ""
content_type
​
The content type attribute to set for each message. This field supports interpolation functions.
Type: string
Default: "application/octet-stream"
content_encoding
​
The content encoding attribute to set for each message. This field supports interpolation functions.
Type: string
Default: ""
metadata
​
Specify criteria for which metadata values are attached to messages as headers.
Type: object
metadata.exclude_prefixes
​
Provide a list of explicit metadata key prefixes to be excluded when adding metadata to sent messages.
Type: array
Default: []
priority
​
Set the priority of each message with a dynamic interpolated expression. This field supports interpolation functions.
Type: string
Default: ""
# Examplespriority: "0"priority: ${! meta("amqp_priority") }priority: ${! json("doc.priority") }
max_in_flight
​
The maximum number of messages to have in flight at a given time. Increase this to improve throughput.
Type: int
Default: 1
persistent
​
Whether message delivery should be persistent (transient by default).
Type: bool
Default: false
mandatory
​
Whether to set the mandatory flag on published messages. When set if a published message is routed to zero queues it is returned.
Type: bool
Default: false
immediate
​
Whether to set the immediate flag on published messages. When set if there are no ready consumers of a queue then the message is dropped instead of waiting.
Type: bool
Default: false
tls
​
Custom TLS settings can be used to override system defaults.
Type: object
tls.enabled
​
Whether custom TLS settings are enabled.
Type: bool
Default: false
tls.skip_cert_verify
​
Whether to skip server side certificate verification.
Type: bool
Default: false
tls.enable_renegotiation
​
Whether to allow the remote server to repeatedly request renegotiation. Enable this option if you're seeing the error message local error: tls: no renegotiation
.
Type: bool
Default: false
Requires version 3.45.0 or newer
tls.root_cas
​
An optional root certificate authority to use. This is a string, representing a certificate chain from the parent trusted root certificate, to possible intermediate signing certificates, to the host certificate.
Type: string
Default: ""
# Examplesroot_cas: |------BEGIN CERTIFICATE-----...-----END CERTIFICATE-----
tls.root_cas_file
​
An optional path of a root certificate authority file to use. This is a file, often with a .pem extension, containing a certificate chain from the parent trusted root certificate, to possible intermediate signing certificates, to the host certificate.
Type: string
Default: ""
# Examplesroot_cas_file: ./root_cas.pem
tls.client_certs
​
A list of client certificates to use. For each certificate either the fields cert
and key
, or cert_file
and key_file
should be specified, but not both.
Type: array
Default: []
# Examplesclient_certs:- cert: fookey: barclient_certs:- cert_file: ./example.pemkey_file: ./example.key
tls.client_certs[].cert
​
A plain text certificate to use.
Type: string
Default: ""
tls.client_certs[].key
​
A plain text certificate key to use.
Type: string
Default: ""
tls.client_certs[].cert_file
​
The path to a certificate to use.
Type: string
Default: ""
tls.client_certs[].key_file
​
The path of a certificate key to use.
Type: string
Default: ""