Preparing this Costframe view
Preparing this Costframe viewA cost anomaly is an unexpected change relative to an appropriate historical and business baseline. It can be a harmful runaway event, an intended deployment, delayed billing, a credit change, or normal seasonality; anomaly does not mean waste.
FinOps + service owner should review this finding before remediation because ownership, dependency, and rollback context often live outside billing data.
Costframe requires read-only billing, resource inventory, and relevant metric access. Missing permissions lower confidence and are shown as limitations.
Review cadence: Daily. Cost and inventory freshness can differ; stale or unavailable evidence must not be treated as a verified saving.
Confidence increases when cost, inventory, utilization, and provider metadata agree. Contradictions or missing telemetry require manual owner review.
Do not quantify savings when billing scope is incomplete, pricing basis is unavailable, utilization evidence is stale, or the resource is part of a planned migration or disaster-recovery design.
A finding is ready only when owner, evidence, risk checks, rollback, approval, and post-change verification are known. Costframe does not execute provider writes.
01 · Cause
02 · Evidence contract
Evidence sources and freshness depend on provider availability, granted read-only permissions, completed audits, and the specific resource type. Missing data lowers confidence; it is not silently converted into a pass.
03 · False-positive review
These conditions lower confidence or require manual owner review before action.
04 · Safe remediation
Rollback is workload-specific: stop the runaway job, restore scaling/configuration, or revert the deployment through the normal incident process. Costframe does not mutate the environment.
05 · Financial truth
An anomaly value is spend variance or exposure, not automatically savings. Savings are counted only after a corrective action and suitable billing verification.
Evidence Ledger example
Synthetic methodology example. It is not a live customer ledger or approved product screenshot; production reports show approved evidence captures inside the authenticated workspace.
Detector FAQ
Trust it when the required evidence is fresh, the owning team agrees the resource is in scope, and the verification path is clear: The cost rate returns to an explained range and the incident/action trail accounts for the variance.
Park it when utilization, billing, ownership, or dependency evidence is incomplete, stale, contradicted, or tied to a planned migration or resilience design.
No. Costframe keeps provider access read-only and presents reviewable evidence and guidance. Customer teams approve and execute changes in their own process.
Check your environment
Review the resource state, source, freshness, confidence limits, and safe next action before anyone changes production.