To read and use OCI Cost Analysis well, you do three things: break spend down by service to see what costs the most, by compartment and tag to see who owns it, and over time to see what is changing. The tool is built into the OCI console and gives you a filterable, groupable view of your bill without exporting anything. The goal is not a pretty chart; it is a short list of the largest, most addressable cost buckets, each with an owner, ready to act on.
This guide is part of our Oracle cloud cluster. For the full set of levers, read the complete guide to Oracle Cloud (OCI) cost optimization, the pillar this article links up to. Reading Cost Analysis is the See step of our See, Cut, Lock, Run method: you cannot cut what you have not first measured and attributed.
Step 1: Group by service to find the big buckets
Open Cost Analysis and group spend by service first. This answers the only question that matters at the start: where does the money actually go? Almost always a handful of services, compute, databases, storage, and networking, make up the bulk of the bill. Sort descending and you have your priority order. There is no point optimizing a service that is two percent of the bill while a service that is forty percent goes unexamined.
Step 2: Group by compartment and tag to find the owner
Cost without an owner is cost no one will cut. Re-group the same spend by compartment and by tag to see which team, environment, or project each dollar belongs to. This is where attribution happens, and where you discover the gaps: spend landing in an untagged or shared bucket that no one owns. If a large share of cost is unattributed, fixing tagging comes before anything else, because every later decision depends on knowing who owns the spend. The sibling guide on OCI compartments and tagging for cost allocation covers how to close those gaps.
By service tells you what is expensive. By compartment and tag tells you who owns it. Over time tells you what is changing. Any one view alone misleads; the three together turn a bill into a plan.
Step 3: View over time to catch trends and spikes
Switch to a time view across at least a few months. A rising line on a single service is an early warning worth chasing before it compounds. A sudden step change usually means something was launched, scaled, or misconfigured, and is often the fastest saving to claw back. Cost Analysis showing month-over-month movement is your cheapest anomaly detector before you set formal alerts.
Step 4: Use filters to test a hypothesis
The real power of Cost Analysis is filtering to answer a specific question. Filter to a single compartment to see what a team spends, to a single service across compartments to see who uses it most, or to a tag to total the cost of a project. Each filtered view is a hypothesis test: is this team overspending on compute, is this environment running overnight when it should not, is this project worth its cost. Work down your priority list from step one, filtering as you go.
Want the read turned into booked savings?
We run Cost Analysis across your tenancy, attribute every dollar, and produce a ranked plan with a value on each line. On the performance model, you pay only from realized savings. No savings, no fee.
Book an OCI cost audit →Step 5: Turn the view into a plan, then guard it
Cost Analysis ends in a list, not a decision. For each big bucket you have identified, name the likely lever: oversized compute goes to rightsizing, cold data to storage tiering, missing commitments to the commitment model. Then set OCI Budgets and alerts on the compartments that matter so the picture you just built stays current and new spikes surface on their own. For the structured pass that turns this view into a sequenced plan, follow the sibling guide on how to run an OCI cost assessment.
| Group by | Question it answers |
|---|---|
| Service | What costs the most? |
| Compartment / tag | Who owns the spend? |
| Time | What is rising or spiking? |
| Filtered view | Is this specific hypothesis true? |
OCI Cost Analysis features, grouping options and the cost-and-usage report reflect the console as of May 2026. Confirm current capabilities and report names in Oracle's documentation before relying on them, as the console evolves.
The OCI Cost Optimization Field Guide includes the Cost Analysis views and saved filters we use to surface waste fast. It is the downloadable companion to this walkthrough.
The short version
Group by service to find the big buckets, by compartment and tag to find the owner, and over time to catch trends, then filter to test specific hypotheses and convert each bucket into a lever and a guardrail. Read three ways, never one. When you want the read run end to end and turned into booked savings by an independent team, that is what our OCI cost optimization service delivers.