Skip to main content
Your cloud spend went up and you want to know why. This guide follows the money from the organisation’s run rate down to the cluster, the change that moved it and the namespace or Stack that costs most, then reads the savings Ankra found and sets a budget so the next rise reaches you before the invoice does. It takes about 15 minutes. Every figure here is an estimate from published prices or your rate cards, less any effective discount you set, as described on Cloud Cost. Use it to find causes and trends, not to reconcile an invoice to the cent.

Before you start

  • Priced clusters. A cluster with no price source reads not priced, never zero; see Get a number for every cluster.
  • The ankra CLI, signed in to your organisation. The steps use it because every organisation has it.
  • billing.manage to add a budget in the last step. Every member can read the figures.
  • The portal’s Cost area is optional: it is in closed beta and enabled per organisation on request. Where it is on, each step names the tab that shows the same figures.

1. See when the run rate moved

summary shows the current run rate and the projected month end. trend draws the run rate per day. Days when the set of priced clusters changed - a cluster created, deleted, stopped, or losing its price - are listed apart: the line moved there without anything being spent. A rise outside those days is real spend. In the portal: Cost → Overview.

2. Find the change that moved it

Events are listed newest first: application releases, node-count changes, scheduled and manual stops and starts, executed cost decisions, clusters entering or leaving pricing, and resolved waste. Each one says how the cluster’s run rate changed between the priced hour before it and the first priced hour at least 30 minutes after it. When several events share that window, such as a release and the scale-up it caused, the move is theirs together and each row says “shared”. Note the cluster named on the events around the day the run rate rose.

3. Read the cluster

This shows the cluster’s totals, the breakdown by component, how the cost is allocated to its namespaces, and whether the cluster is fully priced. Compare the component that grew with the event you noted: more nodes show up as compute, a new volume as storage. In the portal: the cluster’s Cost page, under How the monthly rate is built and Servers in this cluster.

4. Find the workload

namespaces lists the costliest 25 namespaces with their total, latest and peak, so a namespace that grew stands out. object stack prices one Stack on its own; object application and object namespace do the same for an application or a namespace. In the portal: Cost → Explore spend, or Cost by namespace on the cluster’s Cost page. You now know which cluster, which change and which workload. If the rise is expected, such as a new service or more traffic, set a budget in step 6 so the new level is watched.

5. Read what you could save

Each recommendation names its cluster, its estimated monthly saving and its basis: measured (from observed usage), billed (an off-hours stop on billed compute) or estimate (capacity less requests, with no usage measured). The total counts only measured and billed savings, each cluster once at its best lever. The levers are:
  • right-size idle capacity,
  • reduce run rate no namespace claims,
  • stop a known non-production cluster on weeknights and weekends.
Approving and running one of them is a cost decision: see Review, approve and run decisions. Resources that bill while doing no work, such as an unattached volume or a load balancer with no targets, are listed under Orphaned and idle resources. In the portal: Cost → Savings.

6. Set a budget that warns you

--amount is per month. --scope can also be organisation, project, environment (a cluster label) or application; a scope holds one budget.
When the projected month end reaches the notice threshold, Ankra raises a Budget crossing notification; route it to a channel with notification routing. The budget’s owner, or the organisation’s admins when the budget has no owner or the owner is no longer an active member, also gets an email when the month first reaches the threshold, when it is projected past the budget and when it is spent past it.

Verify

Your budget is listed with the month so far, the projected month end and the hour it would cross the budget.

What can go wrong

Next steps