kindling tested by Argusic Runner

What the test found

Kindling collector binary builds and runs continuously in unprivileged container, initializing all analyzers and emitting self-observability JSON metrics to stdout; the eBPF probe cannot load without root/kernel-module permissions, HTTP pprof/metrics endpoints stop serving after ~60s, and pre-existing test failures in DNS/prometheus/k8s tests remain.

eBPF probe (/dev/kindling-falcolib0) requires root and loaded kernel module - unavailable in unprivileged container. All Go unit tests were built (some pre-existing failures). The collector starts, initializes all analyzers, emits self-observability JSON metrics via stdout every ~15s, and the process stays alive for >480s with /proc confirming continuous execution. The HTTP endpoints (pprof :6060, prometheus :9500) respond initially but become unreachable after ~60s, likely from a goroutine panic in the self-metrics output path.

Argusic installed kindling in 47 minutes and launched it; verification reached Verified with mock services. 8 of 8 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of kindling

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.