Benthos serves two HTTP endpoints for health checks:
/pingcan be used as a liveness probe as it always returns a 200.
/readycan 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.
Benthos exposes lots of metrics either to Statsd, Prometheus or for debugging purposes an HTTP endpoint that returns a JSON formatted object.
The target destination of Benthos metrics is configurable from the metrics section, where it's also possible to rename, whitelist or blacklist certain metric paths.
Benthos also emits opentracing events to a tracer of your choice, which can be used to visualise the processors within a pipeline.