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
Can you please let me know how can I get the following info when I am running the tool?
Silent packet drops and black holes
Jitter (average of the deviation from the network mean latency)
PMTU or Firewall issues too related possibly to network config changes (accidental or not)
right now the only thing that I get is:
Reachability
Round-trip and 1-way latency
Thanks
The text was updated successfully, but these errors were encountered:
Arachne is a packet loss detection system and an underperforming path detection system with negligible computational, memory, and traffic overhead.
Specifically, it checks reachability and measures the round-trip and one-way latency, as well as the number of silent packet drops over the multiple available paths between two server end-points, internal or external. Arachne can detect i) intra-DC, ii) inter-DC, iii) Cloud-to-DC, and iv) DC-to-external-services issues by generating a minimal amount of traffic. As examples of external third-party services, one can think of payment, messaging, and mapping services.
Note that the packet drops are currently only uploaded through the metrics lib (e.g. to datadog) and not reported in the 'standalone' stdout.
Additional metrics, such as jitter, i.e., the average of the deviation from the network mean latency or firewall issues, can be deduced from the above basic set of measurements.
What Arachne does not conduct is network bandwidth tests.
Hi,
Can you please let me know how can I get the following info when I am running the tool?
Silent packet drops and black holes
Jitter (average of the deviation from the network mean latency)
PMTU or Firewall issues too related possibly to network config changes (accidental or not)
right now the only thing that I get is:
Reachability
Round-trip and 1-way latency
Thanks
The text was updated successfully, but these errors were encountered: