Skip to content

Network Paths

Network Paths utilize eBPF-based Traceroute detection to display the hop-by-hop network path and detection quality from the source (client) to the destination (server).


Prerequisites

Before using Network Paths, ensure the following steps have been completed:

  1. Register and log in to Guance;
  2. Install DataKit on the host;
  3. Enable the eBPF collector.

Network Paths List

Navigate to Infrastructure > Network > Network Paths to view the detection results of all network paths in the current workspace.

Quick Filters

The left side supports filtering by the following dimensions:

Dimension Field
Path Status Destination Reachable / Partial Path / Detection Failed
Detection Protocol tcp / udp / icmp
Source Host source_host
Source IP src_ip
Source Port src_port
Source Process source_process
Source Service source_service
Destination Domain dst_domain
Destination IP dst_ip
Destination Port dst_port

List Fields

Column Name Description
Path Status Overall detection status, indicated by green/orange/red dots
Source End Source hostname, hover to show IP
Destination Domain Destination domain, shows IP if no domain
Destination Port Destination port, e.g. 443
Protocol tcp / udp / icmp
End-to-End Latency Average RTT from detection source to destination
Packet Loss Rate End-to-end unresponsive ratio
Hop Count Actual TTL hop count
Latest Detection Time Start time of the most recent detection
Options View details

Click a path record in the list to go to the details page.

Network Path Details

The details page displays the detection details of a single network path, including an overview of metrics, a path topology map, historical detection, and node details.

Metrics Overview

Displays key path detection metrics within the current time range:

Metric Description
Path Status Overall completion status of detection

  • Destination Reachable indicates the destination has been reached
  • Partial Path indicates only partial intermediate nodes have been obtained
  • Detection Failed indicates the detection execution is abnormal
  • End-to-End Latency Average round-trip delay (RTT) from detection source to destination, also displays the minimum/maximum latency range
    End-to-End Unresponsive Ratio The proportion of end-to-end detection where no response from the destination is received, the number of detection samples actually sent/received responses is shown in parentheses
    Path Hop Count Number of intermediate nodes the current path passes through (TTL hop count)
    Detection Count Number of Traceroute detection rounds executed in this record

    Path Topology Map

    By default, it displays the hop-by-hop path topology of the latest detection.

    • Source Node: The source initiating the detection, showing information such as source process, service, IP address, and port;
    • Intermediate Nodes (TTL 1, TTL 2 ...): The intermediate network nodes that the packet passes through, showing node name, reachability status, RTT, and attribution information;
    • Destination Node: The destination of the detection.

    Click the upper right corner to switch to the Path Change View to vertically compare results from multiple detections.

    Note

    The RTT of each node in the topology map reflects the round-trip time from the detection source to that node, not the link delay between adjacent hops. Path quality should be based on the End-to-End Latency and End-to-End Unresponsive Ratio at the top.

    Historical Detection

    Below the topology map, a continuous color band shows the distribution of all detection results for this path within the selected time range.

    Color Status Description
    Green Destination Reachable Detection successfully reached the destination
    Orange Partial Path Only obtained partial intermediate nodes
    Red Detection Failed Detection execution exception
    Gray Status Unknown No data or not detected

    Clicking any color block will refresh the metric cards, topology map, and result bar above synchronously to the detection data at that time point. Switching the time widget at the top will re-render the historical detection area. Up to 100 historical records are displayed.

    Node Details

    Click the source node or any intermediate node in the topology map to expand detailed information about that node below, including fields such as IP address, port, host, source process, service, and detection response.

    Note

    If a TTL node displays No Response, it only indicates that the node did not respond to this detection, which may be due to intermediate network device rate limiting, firewall policies, or anonymous routing. It cannot be directly concluded that the device is down or the link is interrupted.

    Feedback

    Is this page helpful? ×