Using LevelFour

Savings Audit

Every saving LevelFour has put in place, what each one saves a month, and who asked for and approved it.

Open Savings Audit in the dashboard sidebar. It holds one table, Savings implemented, with a row for every saving applied so far, across every provider.

The line under the title, Total saved, is the monthly saving of the rows the table lists. It follows your filters and the date window, so the figure and the rows always agree.

What each row shows

  • Savings ID, which opens the recommendation it came from on the Savings page
  • The provider, account and service it applies to
  • When it was implemented
  • The usage type, amount and unit it changed
  • What it saves a month
  • The implementation method it ran through
  • Who requested it and who approved it

Columns shows, hides and reorders these.

Narrow the table

  • Search savings matches the savings ID, provider, account, service, usage type, implementation method, requester and approver.
  • Filter by limits the table to one provider. It appears once more than one provider has savings.
  • More filters narrows by provider, requester, approver, service and implementation method.
  • The date control beside the title limits the table to savings that were saving money inside the window you pick. The Total saved line then names that window.

Export and billing

Download CSV exports the rows the table shows, with the window they cover.

Access Billing opens the Billing page. It does not appear during an evaluation.

A saving reaches this page once it is applied. Approved savings that have not run yet stay under Pending on the Savings page. Approvals and rollout covers that stage.

From other surfaces

  • The MCP server returns realized savings, with who approved them, through get-savings-realized. See Tools
  • Savings is the same data through the SDKs and the REST API

On this page

Ask the FinOps Agent about your cloud spend