Re:Instrumentation: The First Four Things You Measure
by saravana87 on Thursday January 26, 2017 @06:51PM
(#13496522)
TCP retransmission rates looks like a useful metric which can help in monitoring the health of a service. One way to obtain that is by analyzing service interactions as mentioned in the blog. Tracing could be another way through which we can find that info. I am curious as to how code instrumented monitoring solutions get that information.
(PS: I work for Netsil)
[ Parent
| on HN ]
Re:Instrumentation: The First Four Things You Measure
by bbrazil on Thursday January 26, 2017 @08:01PM
(#13496882)
By default you can only get that per-kernel from /proc/net/netsnmp. BPF may allow something more granular.
The other way of approaching it is to look for the additional latency it causes, which you can spot on a per-service basis.
Re:Instrumentation: The First Four Things You Measure
by saravana87 on Friday January 27, 2017 @01:53AM
(#13498218)
Additional latency could be an indicator, but there's no guarantee that it is because of retransmissions ?
Re:Instrumentation: The First Four Things You Measure
by bbrazil on Friday January 27, 2017 @04:35AM
(#13498724)
If you look at your latency histogram and are seeing a bump at around 200ms above normal (which was the default minimum wait time a few years back anyway), it's probably retransmits.
Re:Instrumentation: The First Four Things You Measure
by saravana87 on Friday January 27, 2017 @01:12PM
(#13501436)
Got it.
Re:Instrumentation: The First Four Things You Measure
by rboyd on Thursday January 26, 2017 @07:53PM
(#13496855)
you can get retransmits from 'sar' on linux
Re:Instrumentation: The First Four Things You Measure
by saravana87 on Friday January 27, 2017 @01:46AM
(#13498202)
I see. But, it looks like it is per host and there is no way to find out for a particular service running on the host.