Community

Blog Events Webinars Tutorials Forum
  1. Blog
  2. Events
  3. Webinars
  4. Tutorials
  5. Forum
Create Account
×
Community Blog Introduction to KubeSkoop Exporter

Introduction to KubeSkoop Exporter

This article provides an overview of KubeSkoop Exporter, covering its architecture, metrics, and events.

Overview

KubeSkoop exporter is a network monitoring tool designed for Kubernetes cloud native environments, which can provide the following functions:

  • Pod-level network monitoring, including traffic, application layer connection information, socket memory allocation status, and more.
  • Metrics monitoring for network abnormal states at the Pod level, such as the number of times a Pod's process waits for more than 100ms to read or write to a socket, the number of times a Pod issues TCP RST packets, and so on.
  • At the Pod level, provide on-site observation of network abnormal events and detailed information on the occurrence of events, such as the kernel network soft interrupt scheduling waiting too long, UDP overflow caused by socket memory shortage, and more.

The main differences from common Kubernetes monitoring and observability tools are as follows:

Functions Prometheus Node exporter cAdvisor/Metric API KubeSkoop exporter
By Pod differentiation No Yes Yes
Network status monitoring Yes No Yes
On-site capture of abnormal events No No Yes
Advanced kernel network information No Yes Yes

Introduction

Architecture

1

Information Gathering

KubeSkoop exporter provides adaptation for Kubernetes network monitoring function. On the nodes, KubeSkoop exporter collects and categorizes a large amount of network-related data. The core principle behind these functions includes:

  • Obtaining the network isolation status within the node and its association with Pods through the CRI interface and Linux /proc/.
  • Obtaining network monitoring information through Linux /proc/, Linux netlink, and eBPF.
  • Obtaining the contextual state of the operating system kernel during network anomaly events through eBPF.

Aggregated Analysis

  • Scraping monitoring information through Prometheus and visualizing it using Grafana.
  • Configuring Grafana Loki to receive event push from KubeSkoop exporter and visualizing it using Grafana.
  • Using the KubeSkoop inspector command-line tool to observe monitoring information.

Regarding how to visualize monitoring data, please refer to KubeSkoop exporter visualization.

Metrics

KubeSkoop exporter provides Pod-level metric information to reflect environmental changes during instance operation. Metrics are classified into different probes according to their source and user, and their related information is as follows:

Name Description Granularity Datasource
netdev Exposes network interfaces statistics from /proc/net/snmp. pod procfs
io Exposes process io syscall statistics from /proc/io. pod procfs
tcp Expose tcp basic statistics from /proc/net/tcp pod procfs
softnet Expose softnet statistics from /proc/net/softnet pod procfs
sock Expose sock alloc/memory usage statistics pod procfs
tcpext Expose tcp extended statistics from /proc/net/netstat pod procfs
udp Expose udp basic statistics from /proc/net/snmp pod procfs
tcpsummary Expose tcp diagnosis information pod netlink
ip Expose layer3 ip basic statistics from /proc/net/snmp pod procfs
socketlatency Latency statistics of processing syscall with socket pod eBPF
net_softirq Network softirq schedule and processing latency statistic node eBPF
virtcmdlatency Virtio-net command processing latency statistic node eBPF
kernellatency Latency statistics of processing network packet in kernel stack pod eBPF
netiftxlat Network interfaces tc qdisc processing latency statistic pod eBPF
packetloss Statistics of packet dropping in kernel stack processing pod eBPF

Events

KubeSkoop exporter provides network-related abnormal events occurring on the nodes. Based on our experience in handling network issues in the long-term, we have summarized several common network troubleshooting problems. They often interfere with normal business operations in the cluster in an unpredictable and occasional manner, lacking effective localization methods. Some of them are as follows:

  • Connection failure, response timeout, and other issues caused by discarded network packets.
  • Occasional performance issues caused by longer processing time for network data.
  • Task abnormality issues caused by TCP, conntrack, and other stateful abnormalities.

For network issues that are difficult to quickly reproduce and obtain on-site, KubeSkoop exporter provides eBPF-based operating system kernel context observation capabilities to capture the real-time state of the operating system at the scene of the problem and output it in the form of event logs.

The events supported by KubeSkoop exporter are as follows:

Name Description
netif_txlat Expose slow processing events in tc egress qdisc
packetloss Expose packet dropping events in kernel stack processing
net_softirq Expose NET_RX/NET_TX softirq schedule/processing delay
socketlatency Expose high latency of operating socket from user process
kernellatency Expose netfilter/route delay in kernel
virtcmdlatency Expose high latency virtio-net command processing
tcpreset Expose receiving/sending tcp segments with RST flag

In the information of the event log, relevant information of the event scene can be viewed. Taking the tcp_reset probe as an example, when a Pod receives a normal message on a certain port, KubeSkoop exporter will capture the following event information:

type=TCPRESET_NOSOCK pod=storage-monitor-5775dfdc77-fj767 namespace=kube-system protocol=TCP saddr=100.103.42.233 sport=443 daddr=10.1.17.188 dport=33488

The information in the event is as follows:

  • "type" indicates that an event of TCPRESET_NOSOCK type has occurred, which is a type of event captured by the tcpreset probe. It indicates that a message accessing a certain port was rejected locally by sending an RST message because there was no corresponding socket found based on the message. This event often occurs when NAT fails, or when the ipvs timer times out.
  • "pod/namespace" is the Pod metadata associated with the event by KubeSkoop exporter, which is matched based on the network namespace, IP address, and network device number of the sending message.
  • "saddr/sport/daddr/dport" is the information of the abnormal message obtained by KubeSkoop exporter in the kernel. With different events, this part of the information will also differ. For example, in the event information of the net_softirq probe, there is no IP address, instead, there is the CPU number where the interrupt occurred and the duration of the delay caused by it.

For events that require effective operating system kernel stack information, additional protocol stack information of the operating system kernel can be obtained by configuring the switch, which will increase certain costs and obtain more accurate phenomena, for example:

type=PACKETLOSS pod=hostNetwork namespace=hostNetwork protocol=TCP saddr=10.1.17.172 sport=6443 daddr=10.1.17.176 dport=43018  stacktrace:skb_release_data+0xA3 __kfree_skb+0xE tcp_recvmsg+0x61D inet_recvmsg+0x58 sock_read_iter+0x92 new_sync_read+0xE8 vfs_read+0x89 ksys_read+0x5A
Container Service Open Source Containers Kubernetes cloud native System Monitoring KubeSkoop KubeSkoop Exporter
0 1 0
Share on

Read previous post:

Depth Analysis of Istio Ambient Mesh Traffic Path

Read next post:

Brief Analysis of Envoy Adaptive-Concurrency Filter

Alibaba Cloud Native Community

503 posts | 48 followers

You may also like

Comments

Alibaba Cloud Native Community

503 posts | 48 followers

Related Products

More Posts by Alibaba Cloud Native Community

See All