Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
eBPF-based Cloud Native Monitoring Tool
| Date | Stars |
|---|---|
| 2026-07-24 | 1061 |
| 2026-07-25 | 1061 |
| 2026-07-28 | 1061 |
| 2026-07-30 | 1061 |
| 2026-08-06 | 1061 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# Kindling [](https://github.com/KindlingProject/kindling/blob/main/LICENSE) [](http://kindling.harmonycloud.cn/docs/overview-and-concepts/overview/) [](https://goreportcard.com/report/github.com/KindlingProject/kindling/collector) Visit our [Kindling website](http://kindling.harmonycloud.cn/) for more information. ## What is Kindling Kindling is an eBPF-based cloud native monitoring tool, which aims to help users understand the app behavior from kernel to code stack. With **trace profiling**, we hope the user can understand the application's behavior easily and find the root cause in seconds. Besides trace profiling, Kindling provides an easy way to get an overview of network flows in the Kubernetes environment, and many built-in network monitor dashboards like TCP retransmit, DNS, throughput, and TPS. Not only as a network monitor, but Kindling is also trying to analyze one detail RPC call and get the following information, which can be found in network explore in chrome. And the usage is the same as network exploration in chrome, with which users can tell which part to dig into to find the root cause of the problem in the production environment.  ## What is Kindling Trace-profiling With traces, metrics, and logs, many issues still can’t be understood easily. Trace-profiling is trying to integrate the OnCPU and OffCPU events within the traces and collect the logs output during the trace execution timeframe. OnCPU events are just like the flame graph, but the code has been collected at the thread level instead of the process level. And the trace was executed by one thread, so users can understand how the trace was executing on the CPU. OffCPU events are the opposite of OnCPU events. As for the trace analysis, most traces spend a lifetime waiting for the locks, database query, remote process call, file reading, or file writing. All of these events cause the thread in waiting status, and they are considered as OffCPU events. So for trace profiling, how all threads were executed is recorded and can be replayed. - The exact thread which executed the trace span is highlighted. - The logs printed by each thread are collected and correlated to the relative thread with its timestamp. - The code execution flame graph is correlated to the time series where the CPU is busy. - The network-related metrics are correlated to the time series where the network syscalls are executing. - The file-related metrics are correlated to the time series where the file syscalls are executing. ## Architecture From a high-level view, the agent runs as DeamonSet in Kubernetes. It collects all syscalls and some other tracepoints. We use different exporters for different distributions. For example, we build a Prometheus exporter to export the data which can be stored in Prometheus and displayed in Grafana Plugin. But for the trace profiling module, the UI is different, that's a standalone module.  ## Linux kernel version support The Kindling eBPF module depends on the kernel version which is newer than 4.14. But for trace-profiling, the kernel version has to be newer than 4.17, hoping with more work, the trace-profiling can work on older kernel versions. As an eBPF constraint, the eBPF module can't work for older kernel versions. But for the users who want to try the functionality with the old kernel, we use the kernel module from Sysdig open-source project with enhancement and verification. Basically, the idea is to use a kernel module for tracking the kernel tracepoints. Thanks to Sysdig open-source project, it provides a tracepoint instrument framework for older kernel version
Excerpt of 8,588 characters
Read on GitHub
165
49
36
36
26
21
20
19
7
6
6
4
3
3
3
2
2
1
1
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:9931c5cee0af2d53, topic:observability, topic:monitoring
matched fp:9931c5cee0af2d53, topic:kubernetes