This adds two reports below System/Network/TCP : TCP utilization and TCP errors.
That would have been useful with a customer whose problem was a lot of retrans/s above a certain network traffic.
Errors were not logged at device level, only through sar -n ETCP.
I'm not sure to have found all the places to update, but this seems to work, and with --rotate too.
In the utilization report, I've not found how to put segments (iseg/oseg) both on a 2nd Y axis. As I understand, this is possible only for the last data series. I don't think this is really a problem.
See #141
This adds two reports below System/Network/TCP : TCP utilization and TCP errors.
That would have been useful with a customer whose problem was a lot of retrans/s above a certain network traffic. Errors were not logged at device level, only through
sar -n ETCP
.I'm not sure to have found all the places to update, but this seems to work, and with --rotate too.
In the utilization report, I've not found how to put segments (iseg/oseg) both on a 2nd Y axis. As I understand, this is possible only for the last data series. I don't think this is really a problem.
I've left the DEBUG print , these are so useful.
Real life example: