coroot-node-agent
coroot-node-agent copied to clipboard
coroot
A Prometheus exporter based on eBPF that gathers comprehensive container metrics
Hello, I've encountered an issue with lost samples in the Coroot agent logs related to file_events. The error message is as follows: `E1031 13:21:00.155047 1512321 tracer.go:380] file_events lost samples: 18`...
### docker-compsoe.yml ``` services: node-agent: restart: always image: ghcr.io/coroot/coroot-node-agent:1.27.0 # pull_policy: always privileged: true pid: "host" volumes: - /sys/kernel/tracing:/sys/kernel/tracing - /sys/kernel/debug:/sys/kernel/debug - /sys/fs/cgroup:/host/sys/fs/cgroup - ./data:/data command: - '--collector-endpoint=http://192.168.0.10:8080' - '--cgroupfs-root=/host/sys/fs/cgroup'...
currently, node-agent overwrites listen addr to localhost if configured with MetricsEndpoint, which prevents scraping metrics from it https://github.com/coroot/coroot-node-agent/blob/c0c56bc4abf4ada73bae96a1df98befe77ea64b1/flags/flags.go#L93 not sure if it's done intentionally or not, but it in our...
A significant change occurred in the size of the coroot-node-agent binary, growing from 77.6 MB in version [1.23.15](https://github.com/coroot/coroot-node-agent/releases/tag/v1.23.15) to 189 MB in version [1.23.16](https://github.com/coroot/coroot-node-agent/releases/tag/v1.23.16).
As officially documented, we can label a node to tell in which availability zone it is: * https://kubernetes.io/docs/reference/labels-annotations-taints/#topologykubernetesiozone So, as a result, the label `topology.kubernetes.io/zone` can be used as a...
I have coroot-node-agent on virtual machine via docker. Memery limit is 9Gb ```shell ExecStart=/usr/bin/docker run \ --name=%N \ --rm=true \ --network=host \ --stop-timeout=30 \ --pull=always \ --privileged --pid host \...
Excuse me, how is the parent-child relationship of traceIds generated in the node-agent? I only found the following code. Is the parentTraceId an empty string here? Thank you very much....
coroot-node-agent is flooded logs with messages like: > E0811 07:31:31.181121 1208219 tracer.go:380] python_thread_events lost samples: 5 The issue occurs only on 2 nodes out of 146 in the Kubernetes cluster...
