Skip to content
Browse the documentation

Connect your providers

Connect Oracle Cloud

Read Oracle Cloud Infrastructure spend from its FOCUS cost reports, with an API key CostReveal makes and you upload, and make tags explain who spent it.

CostReveal reads Oracle Cloud spend from the FOCUS cost reports Oracle keeps for every metered tenancy. Nothing is installed in your workloads, no secret of yours is exchanged, and CostReveal can read the cost reports and nothing else.

What you need

  • A metered tenancy. Oracle makes no cost reports for tenancies that are not.
  • An administrator who can create users, groups and policies in the root compartment.
  • An owner or admin role in CostReveal.

Connect

  1. In CostReveal, go to Connections and choose Connect Oracle Cloud. CostReveal makes an API key for this connection and shows its public half and fingerprint. Its private half never leaves CostReveal.
  2. In Oracle's Identity, create a group named costreveal-readers and a user for CostReveal in it. The user needs no password and no console access.
  3. Under the user's API keys, paste CostReveal's public key. Oracle then shows the same fingerprint.
  4. Add the policy statements shown to a policy in the root compartment. The first two let the group read the cost reports, which Oracle keeps in its own tenancy; the third, which is optional, lets CostReveal check every month against Oracle's own total.
  5. Enter the tenancy OCID, the user OCID and the home region, and choose Verify and connect. CostReveal signs in with its key and lists the cost reports before saving anything, and points at the field to fix if it cannot.

Oracle adds cost reports every six hours, and some usage arrives up to a day late. CostReveal reads them every six hours. The first read brings in the current month and the twelve before it, as far as Oracle still holds reports for them. Where Oracle holds no older months, Connections says how far back it reached, and each read asks again.

To stop, delete CostReveal's key from the user, or delete the user. CostReveal then keeps every figure already read and tells you new data has stopped.

How spend is explained

  • Service comes from Oracle, so it is DIRECT.
  • Team, feature and customer come from tags, read with the project's tag keys. Defined tags are keyed by their namespace, such as Operations.CostCenter; name them that way in the project's tag keys to read them.
  • Generative AI spend is shown by service. Oracle's reports name models only in text, so Oracle spend has no model in CostReveal.

Spend that no tag names is shown as unknown, never spread across teams.

How figures are checked

  • Every line is recorded exactly as the report states its billed cost. Each report object is read once, and a month is read again only when Oracle has added or changed an object in it.
  • With the third policy statement, each month is compared with the Usage API's own total for the same usage. While the month is open a difference is pending; once it closes it is flagged. Without it, CostReveal says only that every amount is attributed.

Removing the connection

Removing the connection under Connections deletes every figure it brought in from the project, its archived reports within a day, and CostReveal's key. Delete the key from the user in Oracle too.