You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When collecting data from a server, the iperf3_received_bytes & iperf3_received_seconds are stored in prometheus but if the server is stopped or goes down (or connectivity issues) these metrics are no longer stored in prometheus, only the "e.success" metric is stored with a 0 value.
The problem with this behaviour is that it creates gaps with no measure at all. I believe it would be better to include the
iperf3_received_bytes, iperf3_received_seconds both with 0 value.
When collecting data from a server, the iperf3_received_bytes & iperf3_received_seconds are stored in prometheus but if the server is stopped or goes down (or connectivity issues) these metrics are no longer stored in prometheus, only the "e.success" metric is stored with a 0 value.
The problem with this behaviour is that it creates gaps with no measure at all. I believe it would be better to include the
iperf3_received_bytes, iperf3_received_seconds both with 0 value.
Check the image attached, in red the resulting measure if the iperf3_received_bytes, iperf3_received_seconds are always stored
The text was updated successfully, but these errors were encountered: