Closed gberche-orange closed 1 day ago
This is partly addressed in #35 by exposing the number of failed tests. This tool isn't designed to be a complete interface into iperf, just a way to expose metrics, so I don't think it's appropriate to use it to consume arbitrary error messages.
Expected behavior
As a user, In order to visualize iperf errors in prometheus/grafana I need iperf errors (server unreacheable, server busy) to be exposed as metrics and/or labels
Here is a 1st though with a new counter metric
Current behavior
IPerf does not seem to include errors in the json output, not supporting options to do so, see https://github.com/esnet/iperf/blob/master/docs/invoking.rst
As a result, errors are currently only visible on the container stdout, as shown below