Halaman utama Jelajahi Bantuan
Daftar Masuk
root
/
ebpf
1
0
Fork 0
Berkas Masalah 0 Permintaan Tarik 0 Wiki

Tidak Ada Deskripsi

Pohon: v1.9.0
Ranting Tag
ebpf
ZIP TAR.GZ
Nikolay Sivko 041420e7b6 Merge pull request #27 from coroot/ebpf_l7_go_tls 2 tahun lalu
.github 7d6ad21f2a build: arm64 support 3 tahun lalu
cgroup a091277bc8 add support for CRI-O 3 tahun lalu
common dfb7f3e544 fix detection of k8s volume names mounted with `subPath` 4 tahun lalu
containers 2cf13850e2 eBPF-based TLS connections tracing for Golang applications 2 tahun lalu
ebpftracer 2cf13850e2 eBPF-based TLS connections tracing for Golang applications 2 tahun lalu
flags 2163f5f7a9 cloud metadata: added the ability to set the instance type and lifecycle using CLI arguments or environment variables 3 tahun lalu
logs c96452b9d6 try to determine the actual connection destination using the conntrack table in the container net namespace 3 tahun lalu
manifests 92ef04b486 squashing commits before publishing 4 tahun lalu
node 06edf01e60 using IMDSv2 to retrieve AWS instance metadata 3 tahun lalu
pinger 2bd0422cce pinger uses only SO_TIMESTAMPING to calculate RTT 4 tahun lalu
proc 32c6ad26ab initial support for sandboxed containers (e.g., `gvisor`) 3 tahun lalu
tracing 39716bc510 [mongodb] validating that mongodb messages are not truncated before allocating buffers 2 tahun lalu
.dockerignore 12d24bf447 capturing Postgres queries at the eBPF level 3 tahun lalu
.gitignore 92ef04b486 squashing commits before publishing 4 tahun lalu
Dockerfile 2cf13850e2 eBPF-based TLS connections tracing for Golang applications 2 tahun lalu
LICENSE 92ef04b486 squashing commits before publishing 4 tahun lalu
README.md 212616d40b Update README.md 3 tahun lalu
go.mod 2cf13850e2 eBPF-based TLS connections tracing for Golang applications 2 tahun lalu
go.sum 2cf13850e2 eBPF-based TLS connections tracing for Golang applications 2 tahun lalu
main.go 2cf13850e2 eBPF-based TLS connections tracing for Golang applications 2 tahun lalu

README.md

Coroot-node-agent

Go Report Card License

The agent gathers metrics related to a node and the containers running on it, and it exposes them in the Prometheus format.

It uses eBPF to track container related events such as TCP connects, so the minimum supported Linux kernel version is 4.16.

Features

TCP connection tracing

To provide visibility into the relationships between services, the agent traces containers TCP events, such as connect() and listen().

Exported metrics are useful for:

  • Obtaining an actual map of inter-service communications. It doesn't require integration of distributed tracing frameworks into your code.
  • Detecting connections errors from one service to another.
  • Measuring network latency between containers, nodes and availability zones.

Related blog posts:

Log management is usually quite expensive. In most cases, you do not need to analyze each event individually. It is enough to extract recurring patterns and the number of the related events.

This approach drastically reduces the amount of data required for express log analysis.

The agent discovers container logs and parses them right on the node.

At the moment the following sources are supported:

  • Direct logging to files in /var/log/
  • Journald
  • Dockerd (JSON file driver)
  • Containerd (CRI logs)

To learn more about automated log clustering, check out the blog post "Mining metrics from unstructured logs".

Delay accounting

Delay accounting allows engineers to accurately identify situations where a container is experiencing a lack of CPU time or waiting for I/O.

The agent gathers per-process counters through Netlink and aggregates them into per-container metrics:

Related blog posts:

Out-of-memory events tracing

The container_oom_kills_total metric shows that a container has been terminated by the OOM killer.

Instance meta information

If a node is a cloud instance, the agent identifies a cloud provider and collects additional information using the related metadata services.

Supported cloud providers: AWS, GCP, Azure, Hetzner

Collected info:

  • AccountID
  • InstanceID
  • Instance/machine type
  • Region
  • AvailabilityZone
  • AvailabilityZoneId (AWS only)
  • LifeCycle: on-demand/spot (AWS and GCP only)
  • Private & Public IP addresses

Related blog posts:

Installation

The documentation is available at coroot.com/docs/metric-exporters/node-agent.

Metrics

The collected metrics are described here.

Coroot

The best way to turn metrics to answers about app issues is to use Coroot - a zero-instrumentation observability tool for microservice architectures.

A live demo of Coroot is available at community-demo.coroot.com

License

Coroot-node-agent is licensed under the Apache License, Version 2.0.

The BPF code is licensed under the General Public License, Version 2.0.