coroot-node-agent
coroot-node-agent copied to clipboard
coroot
A Prometheus exporter based on eBPF that gathers comprehensive container metrics
On bare server installation coroot node Agent, all the data returned is such "container_id ="/system. Slice/sshd.service ", all the container_id SSHD. Service tag. Is this where I didn't set it...
https://github.com/coroot/coroot-node-agent/blob/a90fb2df6441b31b0640c63ed60f6a6ab0860bb7/tracing/tracing.go#L90 There may be micro difference between`time.Now()` and the time when connection closed, the former is the processing time, and the latter is the event time. The duration between these...
HTTPS traces cannot be observed？ By the way, can you only retrieve outbound traces? Can't inbound work?
Version: coroot-node-agent-v1.21.4 In the terminal： ``` vagrant@ubuntu2004:/tmp/src$ VM='ubuntu2004' go test -p 1 -count 1 -v ./ebpftracer/... go: downloading github.com/containerd/cgroups v1.0.4 I0910 07:20:22.924156 14920 net.go:20] whitelisted public IPs: [] === RUN...
Version: coroot-node-agent-v1.21.4 Vagrant's error info: ``` Host path: /root/Source/obser/coroot-node-agent-v1.21.4/ Guest path: /tmp/src Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 22 -o LogLevel=FATAL...
When running `coroot-node-agent` directly on an EC2 instance thats part of an ECS cluster, the following message is spammed: `W0905 11:42:31.320648 1826000 registry.go:305] failed to read proc cgroup: unknown container:...
Currently, coroot-node-agent only parses network packets that the current node service actively requests for other services. However, in many scenarios, coroot-node-agent cannot be deployed to all nodes. Can it support...
I can't see anything obvious in the changelogs but it looks like at some point after `1.18.9` support for Linux 4.x Kernels was dropped. We currently run some clusters that...
Initial fix for :- https://github.com/coroot/coroot/issues/606 new metric `container_resources_memory_page_faults_total` to detect memory pressure. the new metrics are correctly exposed on the` /metrics` endpoint, showing both major and minor fault types 
kernel version ``` :~$ uname -r 5.4.0-1063-aws ``` OS version ``` $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.6 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.6 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal...
