OpenCost allocations report zero usage against Coroot Prometheus #2689

Activity

1. devantler

   added

   bug

   automation

   needs investigation

   on Jul 18, 2026
2. github-project-automation

   added this to 🌊 Project Boardon Jul 18, 2026
3. coderabbitai commented on Jul 18, 2026

   

   coderabbitaiBot

   on Jul 18, 2026 – with coderabbitai

   Contributor

   More actions

   🔗 Related PRs

   #2507 - fix(apps): make actual-budget openid schema offline-resolvable [merged]
   #2527 - feat: install the OpenFeature Operator (runtime feature-flag layer) [merged]
   #2554 - chore(deps): update helm release opencost to v2.5.26 [merged]
   #2555 - fix(opencost): patch ui probe timeouts [merged]
   #2578 - fix(policy-reporter): run all components at the HA replica floor [merged]

   ---

   📝 Issue Planner

   _{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

   • Create Plan

   ---

   🧪 Issue enrichment is currently in open beta.

   You can configure auto-planning by selecting labels in the issue_enrichment configuration.

   To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

   issue_enrichment:
     auto_enrich:
       enabled: false
   

   💬 Have feedback or questions? Drop into our discord!
4. devantler

   moved this to 🫴 Ready in 🌊 Project Boardon Jul 18, 2026
5. devantler

   added the

   Bug

   issue type on Jul 18, 2026
6. devantler

   moved this from 🫴 Ready to 📥 Backlog in 🌊 Project Boardon Jul 18, 2026
7. devantler commented on Jul 22, 2026

   

   devantler

   on Jul 22, 2026

   ContributorAuthor

   More actions

   🤖 Generated by the Agentic Engineer

   Read-only revalidation on 2026-07-22 narrows the failure to an incompatible metrics input, not OpenCost-to-Prometheus reachability:

   • The 3-day allocation still returns 34 namespaces, but cpuCoreUsageAverage sums to zero across all of them.
   • Coroot Prometheus returns 339 kube_pod_container_resource_requests{resource="cpu"} series, but zero container_cpu_usage_seconds_total series and no 5-minute container CPU rate.
   • The live coroot-prometheus deployment config only self-scrapes 127.0.0.1:9090; its other data arrives through remote write. The required cAdvisor/container-usage series are not present in that TSDB.
   • OpenCost is healthy and explicitly points PROMETHEUS_SERVER_ENDPOINT at this Coroot Prometheus service.

   So the current root cause is the metrics contract: the configured Prometheus source has kube-state request data but does not ingest the container usage series OpenCost needs. Rightsizing remains correctly fail-closed until a compatible usage source is supplied and the proposed regression check proves non-zero usage for active namespaces.
8. devantler

   self-assigned this

   on Jul 23, 2026
9. github-project-automation

   moved this from 📥 Backlog to 👀 In Review in 🌊 Project Boardon Jul 23, 2026
10. devantler

    marked fix(opencost): usage metrics are absent for every namespace, so efficiency and rightsizing are unmeasurable #2782 as a duplicate of this issue on Jul 23, 2026
11. devantler

    added a commit that references this issue on Jul 27, 2026

    chore: claim #2689

    1d8e753
12. devantler

    closed this as completedin #2827on Jul 27, 2026
13. github-project-automation

    moved this from 👀 In Review to ✅ Done in 🌊 Project Boardon Jul 27, 2026