Most budget incidents in LLM systems still get framed as demand spikes or model volatility. The primary-source threads suggest a different ordering: guardrail integrity and attribution joins break first.
This note uses only open maintainer/operator threads and is aimed at AI platform and FinOps owners who need a practical triage order.
1) False 429 incidents can be reservation-drift bugs, not real overspend
Source: https://github.com/BerriAI/litellm/issues/27639 (open, updated 2026-05-19)
The reported pattern is operationally dangerous: intermittent BudgetExceededError, DB spend near zero, Redis counters accumulating phantom reservations, and temporary relief after key flushes before drift returns.
If this class of drift exists, policy enforcement becomes a reliability incident generator. Teams then lose trust in budget controls and start adding manual bypasses.
2) Cost governance is still blocked at token-throughput joins
Source: https://github.com/opencost/opencost/issues/3533 (open, updated 2026-04-06)
The unresolved questions are concrete: tokens per second per GPU/pod, cost per token by phase, and efficiency per dollar across workloads. Spend totals without output-normalized joins provide accounting, not optimization.
3) Tenant chargeback trust breaks when metadata cannot drive native breakdowns
Source: https://github.com/langfuse/langfuse/issues/12614 (open, updated 2026-05-14)
The multi-tenant pain is specific: org identifiers live in metadata, but dashboards cannot use those metadata keys as breakdown dimensions for requests, latency, and token usage. That pushes teams into exports and manual transforms where disputes multiply.
Practical sequence
- Verify 429 integrity before tuning policy limits.
- Establish one reproducible token-throughput cost join for a critical workflow.
- Ensure tenant breakdowns are auditable in the same surface used by platform and finance.
Standards dependency context is still moving as well:
- OTel GenAI semantic conventions for agentic systems: https://github.com/open-telemetry/semantic-conventions-genai/issues/35
- FOCUS validator alignment with 1.4 requirements model: https://github.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/issues/1984
I also packaged a deeper source-led evidence review with claim-to-snippet traceability and intervention checklisting. If useful, reply with your current failure pattern and I can map it to the closest evidence cluster.