pipeline: processors: - mapping: | root.message = this root.meta.link_count = this.links.length() root.user.age = this.user.age.number()

output: redis_streams: url: tcp://TODO:6379 stream: baz max_in_flight: 20

### Delivery Guarantees

Delivery guarantees can be a dodgy subject. Bento processes and acknowledges messages using an in-process transaction model with no need for any disk persisted state, so when connecting to at-least-once sources and sinks it's able to guarantee at-least-once delivery even in the event of crashes, disk corruption, or other unexpected server faults.
This behaviour is the default and free of caveats, which also makes deploying and scaling Bento much simpler.
Supported Sources & Sinks
AWS (DynamoDB, Kinesis, S3, SQS, SNS), Azure (Blob storage, Queue storage, Table storage), GCP (Pub/Sub, Cloud storage, Big query), Kafka, NATS (JetStream, Streaming), NSQ, MQTT, AMQP 0.91 (RabbitMQ), AMQP 1, Redis (streams, list, pubsub, hashes), Cassandra, Elasticsearch, HDFS, HTTP (server and client, including websockets), MongoDB, SQL (MySQL, PostgreSQL, Clickhouse, MSSQL), and [you know what just click here to see them all, they don't fit in a README][about-categories].
Connectors are being added constantly, if something you want is missing then open an issue.
Documentation
If you want to dive fully into Bento then don't waste your time in this dump, check out the [documentation site][general-docs].
For guidance on how to configure more advanced stream processing concepts such as stream joins, enrichment workflows, etc, check out the [cookbooks section.][cookbooks]
For guidance on building your own custom plugins in Go check out the section Plugins.
Install
We're working on the release process, but you can either compile from source or pull the docker image:

For more information check out the [getting started guide][getting-started].

Run

Or, with docker:

Using a config file

Using a series of -s flags

## Monitoring
Health Checks
Bento serves two HTTP endpoints for health checks:
/ping can be used as a liveness probe as it always returns a 200.

/ready can be used as a readiness probe as it serves a 200 only when both the input and output are connected, otherwise a 503 is returned.

Metrics

Bento [exposes lots of metrics][metrics] either to Statsd, Prometheus, a JSON HTTP endpoint, [and more][metrics].
Tracing
Bento also [emits open telemetry tracing events][tracers], which can be used to visualise the processors within a pipeline.
Configuration
Bento provides lots of tools for making configuration discovery, debugging and organisation easy. You can [read about them here][config-doc].
Build
Build with Go (any currently supported version):

## Lint

Bento uses [golangci-lint][golangci-lint] for linting, which you can install with:

Check the GitHub Action for what version is currently used in CI.

And then run it with make lint.

Plugins
It's pretty easy to write your own custom plugins for Bento in Go, for information check out [the API docs][godoc-url] and for inspiration there's a set of [plugin examples][plugin-examples] demonstrating a variety of plugin implementations. For help on how to set up your own distribution of Bento then checkout the [plugin example module][plugin-example-module].
Extra Plugins
By default Bento does not build with components that require linking to external libraries, such as the zmq4 input and outputs. If you wish to build Bento locally with these dependencies then set the build tag x_bento_extra:

With go

Using make

Note that this tag may change or be broken out into granular tags for individual components outside of major version releases. If you attempt a build and these dependencies are not present you'll see error messages such as ld: library not found for -lzmq.
Docker Builds
There's a multi-stage Dockerfile for creating a Bento docker image which results in a minimal image from scratch. You can build it with:

Then use the image: