kindling
eBPF-based Cloud Native Monitoring Tool
Runs with mockssource: GitHubhomepageGoApache-2.0commit 034a8ce086e3
Go, Apache-2.0 licensed. The project labels itself: ebpf, kubernetes, monitoring, observability and profiling.
kindling runs, with stand-ins for the services it depends on. An Argusic agent installed it in 14 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The kindling-collector Go binary builds and runs in the container, serving Prometheus metrics on port 9500 (HTTP 200) and initializing all analyzers (network, tcpmetric, tcpconnect, cpu, k8sinfo), with the cgo receiver linked against a stub libkindling.so because the real C++ eBPF probe cannot be compiled without Qt5 development headers.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go compiler not found in container3 minutes
- libkindling.so linking target missing - C++ probe build requires Qt5 dev packages (not available, only Qt6 runtime is installed)3 minutes
- Git submodule probe/libs/agent-libs not initialized1 minute
- C++ probe build (CMake) fails: find_package(Qt5) cannot find Qt5Config.cmake - Qt5 development headers not installable without root
- Install time
- 14 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- curl -s -o /dev/null -w %{http_code} http://localhost:9500/metrics returned 200; go build -o /tmp/kindling-collector ./cmd/kindling-collector/ exited 0 producing a 58MB binary; go test reports 12 packages passing (aggregator, compare, component, analyzer, cpuanalyzer, network/protocol, http, mysql/tools, rocketmq, tcpconnectanalyzer/internal, tools, pyroscopeexporter, aggregateprocessor, cgoreceiver)
- Model tokens used
- 180,984
- Exact commit tested
- 034a8ce086e3
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
ok github.com/Kindling-project/kindling/collector/pkg/component/analyzer/tcpconnectanalyzer/inte… ok github.com/Kindling-project/kindling/collector/pkg/component/analyzer/tools 0.004s ok github.com/Kindling-project/kindling/collector/pkg/component/consumer/exporter/pyroscopeexpor… ok github.com/Kindling-project/kindling/collector/pkg/component/consumer/processor/aggregateproc… ok github.com/Kindling-project/kindling/collector/pkg/component/receiver/cgoreceiver 0.940s === Done === Let me clean up the stub file and compile the final answer. 2026-11-19T13:33:35.006495Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce… Now I have all the data needed. Let me compile the final report. tokens used 180,984 Now I have all the data needed. Let me compile the final report.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 14 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Of the 4 ebpf projects Argusic has installed and timed, kindling was the 2nd fastest to reach a running state, and 2 of 4 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.13 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 1.18 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/kindling)Questions
- Does kindling run?
- kindling runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 14 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test kindling?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 034a8ce086e3. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test kindling?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does kindling take to install?
- 14 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does kindling need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing kindling?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does kindling compare with the alternatives?
- Of the 4 ebpf projects Argusic has installed and timed, kindling was the 2nd fastest to reach a running state, and 2 of 4 reached one at all.
- Where is the evidence for kindling?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.