Add the Binjovi CPU and off-CPU profiling canary #65
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/pipeline-profiles-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?
Add a separate Alloy profiler on the Binjovi BuildKit node and a private Pyroscope store with seven-day retention. Use immutable image digests, bounded resources, and pod discovery limited to the three canary namespaces. The existing log collector stays unchanged.
Profiles are labeled as shared container data until exact task bindings exist. Fleet expansion requires the measured overhead gate.
Validation: Alloy 1.19.2 validates the configuration; Pyroscope 2.3.1 passes a local readiness test with the v1 write path; Kubernetes server dry-run; Olly checks.