Skip to content

Summary

On the Summary page, the system combines time series trend charts and network path data lists to display network traffic and data connection details between clients and servers for four infrastructure types: HOST, Pod, Deployment, and Service.

  • Time Series Chart: Chart showing trend changes of network metrics over different time periods, supports switching to view sent/received bytes, TCP latency/jitter, TCP retransmission count/connection count/close count.
  • Network Path List: Includes information on client, server, sent bytes, received bytes, TCP latency, TCP retransmission count, etc.

Page Overview

Quick Filtering

On the left side of the Summary page, you can quickly filter data based on the following dimensions:

1. Basic Dimensions

  • Transport Protocol: TCP / UDP
  • Traffic Direction: incoming / outgoing
  • HOST: source or destination host name
  • PID: process ID
  • Process: process name

2. Client Dimensions

  • IP: client IP address
  • Port: client port
  • IP Type: IPv4 / IPv6
  • Pod Name: Kubernetes Pod identifier
  • Namespace: Kubernetes Namespace
  • Deployment Name: Deployment identifier
  • Service Name: Service identifier

3. Server Dimensions

  • IP: server IP address
  • Port: server port
  • Domain Name: server domain name
  • IP Type: IPv4 / IPv6
  • Pod Name: Kubernetes Pod identifier
  • Namespace: Kubernetes Namespace
  • Deployment Name: Deployment identifier
  • Service Name: Service identifier

Combinations of Traffic Direction and Transport Protocol

Currently supports network performance monitoring based on TCP and UDP protocols. Combined with incoming and outgoing, there are 6 combinations to choose from:

  • incoming + no protocol distinction
  • incoming + TCP protocol
  • incoming + UDP protocol
  • outgoing + no protocol distinction
  • outgoing + TCP protocol
  • outgoing + UDP protocol

Detail Page

Click a network data entry in the list to enter the Detail page.

Network Analysis

Click the Network Analysis tab on the Detail page to view network performance metric trends and connection details between the client and server.

Metric Overview

Displays key network metric statistics within the current time range:

  • Sent Bytes
  • Received Bytes
  • TCP Connection Count
  • TCP Retransmission Count
  • TCP Close Count

Trend Chart

Provides multi-dimensional time series trend charts, supports switching to view:

  • Sent/Received Bytes: network traffic change trend
  • TCP Latency/TCP Jitter: network delay and jitter
  • TCP Retransmission Count/TCP Connection Count/TCP Close Count: connection quality metrics

Network Connection Analysis

The list below displays specific network connection data:

  • Search: supports keyword search filtering
  • Aggregate by IP Dimension: check to aggregate statistics by IP address, improving query efficiency and avoiding excessive data volume
  • Display Settings: click the "Settings" button to flexibly configure the fields displayed in the list

The list displays key connection metrics such as client, server, sent bytes, received bytes, TCP latency, TCP retransmission count, etc.

Network Flow

Click the Network Flow tab on the Detail page to view detailed network connection data packets between selected hosts.

The top of the page displays the relationship between the currently selected host and server_name.

Toolbar Operations

  • Time Widget: supports selecting a relative time (e.g., last 1 day) or absolute time range
  • Search: automatically applies the current Detail page filter conditions; supports DQL syntax queries, you can enter conditions such as host: or server_name: for precise filtering
  • Jump to Network Flow: click the button in the upper right corner to enter the independent Network Flow page
  • Display Items: click the button on the right to customize which list fields are shown or hidden

Data List

Displays network flow metrics such as time, client, server, traffic direction, PID, HOST, network type, service, sent bytes, received bytes, TCP retransmission count, TCP connection count, etc.

Network Path

Click the Network Path tab on the Detail page to view the hop-by-hop network path and probe quality from the source (client) to the destination (server).

Metric Overview

Displays key path probe metrics within the current time range:

Metric Description
Path Status Overall probe completion status

  • Target Reachable indicates that the hop-by-hop probe has reached the destination
  • Partial Path indicates that only some intermediate nodes were obtained, and the destination was not confirmed to be reached
  • Failed indicates that the probe execution was abnormal
    		•
    End-to-End Latency Average round-trip time (RTT) from the probe source to the destination, also showing the minimum/maximum latency range. This value is calculated by independent end-to-end probes, reflecting the overall link quality
    End-to-End No Response Ratio Ratio of probes that did not receive a response from the destination in end-to-end probes. The actual number of sent/received probes is shown in parentheses (e.g., 10 / 10). This ratio only represents the end-to-end probe result and does not equal the actual packet loss rate of any intermediate router
    Path Hop Count Number of intermediate nodes (TTL hops) the path passes through. If multiple probes exist, average/minimum/maximum hop counts are shown
    Probe Count Number of Traceroute probe rounds executed for this record (e.g., Total 3 rounds of probes). Each round of probes starts from TTL 1 independently to observe path stability
    About Latency and No Response

    The page displays two latency concepts:

    • End-to-End Latency: latency in the metric card, reflecting the overall round-trip time from the probe source to the destination.
    • Single-Hop RTT: RTT of each node in the topology graph, reflecting the round-trip time from the probe source to that intermediate node. It is not the link latency between two adjacent hops.

    Path Topology Graph

    By default, displays the hop-by-hop path topology of the latest probe. Click the upper right corner to switch to the Path Change View to compare paths from multiple probes.

    1. Topology Graph Elements Description:

    • Source Node: the source that initiates the probe, showing source process, service, IP address, port, etc.

    • Intermediate Nodes (TTL 1, TTL 2, ...): intermediate network nodes that the data packet passes through. Each node displays:

      • Node Name: preferentially displays the reverse DNS domain name; if missing, displays the IP address; if still missing, displays a placeholder TTL n
      • Reachability Status: whether the node responded to this probe
      • RTT: round-trip latency from the probe source to this node (in milliseconds)
      • Attribution Information: if it is a public IP, may display the ASN organization name and cloud provider attribution

    • Node Connections: indicate the sequential relationship of the probe path. The connections themselves do not carry link-level latency or packet loss data.

    2. Path Change View:

    When multiple probes exist, switching to the Path Change View allows you to vertically compare the results of each probe round. The system aligns nodes from different rounds based on TTL + IP address, helping you observe whether routing changes (e.g., ECMP multi-path scenarios).

    Historical Probes

    Below the topology graph, a continuous color band displays the distribution of all probe results for the path within the selected time range.

    Color Status Description
    Green Target Reachable Probe successfully reached the destination
    Orange Partial Path Only some intermediate nodes obtained
    Red Probe Failed Probe execution abnormal
    Gray Status Unknown No data or not probed

    Click any color block; the metric cards above, topology graph, and result bar will refresh to show the probe data for that time point. Switching the top Time Widget will re-render the historical probe area. Up to 100 historical records are displayed.

    Node Details

    Click the Source Node or any intermediate node in the topology graph; detailed information for that node will expand below:

    Field Description
    IP Address IP address of the node
    Port Source or destination port
    HOST Name of the source host that discovered the path
    Source Process Name of the process that generated the network traffic (dynamic discovery scenarios)
    Service Name of the service that generated the network traffic (dynamic discovery scenarios)
    Probe Response Response status of this node in the current probe, e.g., Response Received or No Response
    Note
    1. If a TTL node displays No Response, it only means that the node did not return a response to this probe, possibly due to intermediate network device rate limiting, firewall policies, or anonymous routing. It cannot be directly judged as device failure or link interruption.
    2. The topology graph does not display "link latency" or "link packet loss" between adjacent nodes. For path quality, please refer to the End-to-End Latency and End-to-End No Response Ratio at the top.
    3. Some fields (such as Network Operator, cloud provider, Domain Name Resolution, source process/service) depend on the Collector version or platform data supplementation capability. If they are missing, this is normal and does not indicate data anomalies.

    You can view the HOST, Pod, or other related views associated with the current network data.

    Feedback

    Is this page helpful?