keepalived_exporter
coroot-node-agent
| keepalived_exporter | coroot-node-agent | |
|---|---|---|
| 1 | 8 | |
| 42 | 275 | |
| - | 3.3% | |
| 5.8 | 8.3 | |
| 3 months ago | 6 days ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
keepalived_exporter
-
[Question] Running keepalived as non root user
This looks like a promising starting point: https://github.com/gen2brain/keepalived_exporter/issues/5
coroot-node-agent
-
Infra mapping
Our product can do that. It's based on an eBPF Prometheus exporter and doesn't require manual integration.
-
Delay accounting: an underrated feature of the Linux kernel
Node-agent gathers per-TGID statistics from the kernel through the Netlink protocol and aggregates it to the per-container metrics:
- node-agent - an open-source Prometheus exporter based on eBPF that gathers comprehensive container metrics: log summaries, container-to-container network latency, cloud meta-information, etc.
-
How ping measures network round-trip time accurately using SO_TIMESTAMPING
While working on node-agent, we set out to measure network latency between containers and the services they communicate with. Since the agent has already discovered the endpoints that each container communicates with, we just need to measure network latency. We embedded "pinger" directly into the agent to measure end-to-end latency because the ICMP Echo requests should be sent from within the network namespace of each container.
-
Building a service map using eBPF
To address said disadvantages, we implemented eBPF-based container tracing which is a part of our open source Prometheus exporter node-agent. It passively monitors all TCP connections on a node, associates every connection with the related container, and exports metrics in Prometheus format:
-
Mining metrics from unstructured logs
At Coroot, we implemented an automated log parsing in our open-source Prometheus exporter node-agent. To explain how it works, let's follow the same steps as I mentioned above.
- Show HN: A Prometheus exporter that gathers сomprehensive containers' metrics
What are some alternatives?
prometheus-podman-exporter - Prometheus exporter for podman environments exposing containers, pods, images, volumes and networks information.
klog - Leveled execution logs for Go (fork of https://github.com/golang/glog)
ambientweather-local-server - A server for receiving metrics from your local Ambient Weather Console and exposing them as Prometheus Metrics
loghub - A large collection of system log datasets for AI-driven log analytics [ISSRE'23]
logstash-exporter - Prometheus exporter for Logstash written in Go
coroot-aws-agent - A prometheus exporter that gathers metrics from AWS services.
mtail - extract internal monitoring data from application logs for collection in a timeseries database
omada_exporter - Prometheus Exporter for TP-Link Omada Controller SDN.