feat(profiles): enable exact process context and syscall summaries on the canary #69
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/pipeline-syscall-canary-20260909"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Start the Binjovi process collector before Alloy on the single canary worker. A startup check verifies kernel syscall counts and process cleanup. The collector shares the standard OTel trace context map with Alloy and exports bounded syscall summaries to the private profile store.
The binary is pinned to verified Binjovi v0.1.527. Collector metrics expose registration failures, archive failures, and kernel losses. Pod metadata permissions stay read-only. Repository checks, pinned Alloy config validation, and Kubernetes server dry-run pass. The BuildKit runtime hook is enabled in its Flux owner as the next step; fleet rollout still requires the overhead gate.