An input is a source of data piped through an array of optional processors:
Some inputs have a logical end, for example a
csv input ends once the last row is consumed, when this happens the input gracefully terminates and Benthos will shut itself down once all messages have been processed fully.
It's also possible to specify a logical end for an input that otherwise doesn't have one with the
read_until input, which checks a condition against each consumed message in order to determine whether it should be the last.
Only one input is configured at the root of a Benthos config. However, the root input can be a broker which combines multiple inputs and merges the streams:
Inputs have an optional field
label that can uniquely identify them in observability data such as metrics and logs. This can be useful when running configs with multiple inputs, otherwise their metrics labels will be generated based on their composition. For more information check out the metrics documentation.
Sometimes it's useful to consume a sequence of inputs, where an input is only consumed once its predecessor is drained fully, you can achieve this with the
It's possible to generate data with Benthos using the
generate input, which is also a convenient way to trigger scheduled pipelines.
Inputs that consume from storage or message streaming services.amqp_0_9amqp_1aws_kinesisaws_s3aws_sqsazure_blob_storageazure_queue_storagegcp_pubsubhdfskafkakinesismqttnatsnats_streamnsqredis_listredis_pubsubredis_streams
Inputs that consume directly from low level network protocols.http_clienthttp_servernanomsgsocketsocket_serverwebsocketzmq4
Inputs that consume from Google Cloud Platform services.gcp_pubsub
Inputs that provide utility by generating data or combining/wrapping other inputs.brokerdynamicgenerateinprocread_untilresourcesequencesubprocess