Skip to main content

Network performance metrics

It describes the metrics indicators that are collected by Network Performance Monitoring. You can search in Sitemap > Metrics Search. Network performance metrics provide all data folded into fields.

npm_process_tag_data

It indicates the network communication metric for each session. The collection interval is 1 minute.

Field nameUnitDescriptionRemarks
app_name-Custom identification tag for the communicating entityDefault
- A single Linux server environment: Host name
- Kubernetes container environment: Pod name
avg_jittermsAverage of packet round-trip latency fluctuationsAverage jitter over the collection interval
avg_latencymsAverage packet round-trip latency timeAverage latency over the collection interval
container_name-Name of the container collected in the Kubernetes environmentEmpty value if not in Kubernetes environment
direction-Session connection directionIN(Inbound), OUT(Outbound)
foreign_container_id-ID of the container for local communication in the Kubernetes containerDuring local communication, the target cannot be identified using the IP address and port number. Therefore, additional data is provided to find the exact target.
foreign_ip-Target IP address-
foreign_pod_id-Pod ID in case of local communication within a Kubernetes PodDuring local communication, the target cannot be identified using the IP address and port number. Therefore, additional data is provided to find the exact target.
foreign_port-Target port numberClient Port (Inbound - foreign_port) is displayed with data merged to 0.
host_tag-Source host name-
local_ip-Source IP address-
local_port-Source port numberClient Port (Outbound - local_port) is displayed with data merged to 0.
lost_countcountNumber of lost packets-
max_jittermsMaximum for packet round-trip latency fluctuationsMaximum for jitters collected for a certain period
max_latencymsMaximum packet round-trip latency timeMaximum for latencies collected for a certain period
min_jittermsMinimum for packet round-trip latency fluctuationsMinimum for jitters collected for a certain period
min_latencymsMinimum packet round-trip latency timeMinimum for latencies collected for a certain period
pod_name-Pod name in case the communication source is in the Kubernetes environmentEmpty value if not in Kubernetes environment
process_type-Type of process for communication-
protocol-Communication protocol typeTCP / UDP
recv_packet_countcountNumber of received packets-
recv_packet_sizebyteData size of the received packet-
retransmission_countcountNumber of retransmitted packets-
row_countcountSession count including duplicates-
send_packet_countcountNumber of transmitted packets-
send_packet_sizebyteTotal size of the transmitted packets-
session_countcountSession count excluding duplicatesThe number of unique sessions is calculated as HyperLogLog(1) rather than a simple sum.
session_count_lobits-Bit data (HyperLogLog) for calculation of the unique sessionIt is HyperLogLog related information for statistical processing.
tot_jittermsSum of packet round-trip latency fluctuations-
tot_latencymsSum of packet round-trip latencies-
Note

(1): HyperLogLog is a probabilistic data structure that estimates the number of elements in a set with very little memory.

npm_process_tag_list

This is internal data for processing foreign area tagging in the session.

  • Tag lists for each session
  • Collection interval: 1 minute
Field nameDescriptionRemarks
foreign_app_nameCustom identification value of the targetDefault
- A single Linux server environment: Host name
- Kubernetes container environment: Pod name
foreign_container_idID of the container for local communication in the Kubernetes container-
foreign_container_nameContainer name in case the target is in the Kubernetes environment-
foreign_host_tagTarget host name-
foreign_ipTarget IP address-
foreign_pod_idPod ID in case of local communication within a Kubernetes Pod-
foreign_pod_namePod name in case the communication target is in the Kubernetes environment-
foreign_portTarget port number-
foreign_process_typeTarget process nameuntagged if not identified
local_inbound_checkChecks whether the inbound communication works in the internal network.-