Streams Mode

A Benthos stream consists of four components; an input, an optional buffer, processor pipelines and an output. Under normal use a Benthos instance is a single stream, and these components are configured within the service config file.

Alternatively, Benthos can be run in --streams mode, where a single running Benthos instance is able to run multiple entirely isolated streams. Adding streams in this mode can be done in two ways:

  1. Static configuration files allows you to maintain a directory of static stream configuration files that will be traversed by Benthos.

  2. An HTTP REST API allows you to dynamically create, read the status of, update, and delete streams at runtime.

These two methods can be used in combination, i.e. it's possible to update and delete streams that were created with static files.

Metrics

Metrics from all streams are aggregated and exposed via the method specified in the config of the Benthos instance running in --streams mode, with their metrics prefixed by their respective stream name.

For example, a Benthos instance running in streams mode with the configured prefix benthos running a stream named foo would have metrics from foo registered with the prefix benthos.foo.

This can cause problems if your streams are short lived and uniquely named as the number of metrics registered will continue to climb indefinitely. In order to avoid this you should either limit the streams that register their metrics with whitelist or blacklist rules:

# Only register metrics for the stream `foo`. Others will be ignored.
metrics:
  whitelist:
    paths:
    - foo
    child:
      type: prometheus
      prefix: benthos

Or use rename rules to set the same prefix for groups of streams:

# Rename all stream metric prefixes of the form `foo_<uuid_v4>` to just `foo`.
metrics:
  rename:
    by_regexp:
    - pattern: "foo_[0-9\\-a-zA-Z]+\\.(.*)"
      value: "foo.$1"
    child:
      type: prometheus
      prefix: benthos