The documentation seems to indicate that system.net.tcp.retrans_segs and similar metrics are measured as gauges. However, it seems that it's actually being measured as a rate in the network check. I understand that rates are stored as gauges, and that a rate is simply storing the difference between the previous and current value, but since it's time normalized it can result in odd values.

For example, we typically see things like 10.62 retransmitted segments even when using a rollup with sum. This could also simply be to due to the fact that the measured interval using for normalization could be different than the flush interval pass into the flush method.

Using a monotonic count seems more appropriate here. Although, I could also see the rate being useful as well.