As part of “Cloudability for OCI – cost management” launched on September 14th, we would like to share with you some frequently asked questions regarding the way we ingest and map OCI data into our system.
What is currently supported with this integration?
This integration enables customers to:
- Add credentials for their OCI tenancies
- Allocate their spend with Business Mappings, Account Groups, and Tag & Label mappings
- Analyze their OCI spend alongside other cloud spend in a single pane of glass across TrueCost Explorer, Tag Explorer, Reports & Dashboards, and ApptioBI.
- Create a personalized experience for stakeholders using Cloudability Views
- Detect unusual spending patterns with anomaly detection
- Define budgets covering OCI spend and receive alerts for forecasted overspend
Please note that we have created OCI report templates in Cloudability Reports and ApptioBI.
Once my OCI credential is validated, how many months of data will be ingested into Cloudability?
By default, you will get the current month of OCI data after your credentials are validated. If you would like additional months of data ingested, please reach out to your Apptio account team to kick off this process.
What cost metrics are supported for OCI?
The only cost metric required for OCI cost management is cost (total) due to the fact OCI doesn’t have any complexities around amortizing commitments or representing custom pricing. Where applicable, the other cost metrics within Cloudability will simply display the cost (total) value.
How do I get my compartment data into Cloudability?
You can get your compartment information by leveraging dedicated tag keys that we’ve created. We have created a tag key for compartment name, called “cldy:oci:CompartmentName” and a tag key for compartment ID, called “cldy:oci:CompartmentId”.
After your OCI data is ingested in Cloudability, you will be able to map these tags in Tag & Label mapping. We recommend associating each tag with a Cloudability dimension, as demonstrated by the example below:
After mapping these tags, you will need to request data reprocessing for reporting dimensions to be populated.
Please note that we have also created a 3rd dedicated tag key, for OCI subscription ID, called “cldy:oci:SubscriptionId” which can be mapped using the same process.
How do I get a single view across my OCI compartments and my AWS accounts, Azure subscriptions or GCP projects?
We are currently mapping OCI Tenancies to the “Account Name” dimension, which is used to represent AWS Accounts, Azure Subscriptions and GCP Projects.
If you'd like to use a single dimension that covers both OCI compartment names and AWS account names, for example, you can do this by defining a specific business dimension like this example below:
You would then add 2 statements (remember to save them before saving your business mapping):
Statement 1: Set the dimension to your “Compartment Name” tag dimension. Set the operator to “exists” and leave the value empty.
Statement 2: Set the dimension to the Cloudability “Account Name” dimension. Set the operator to “exists” and leave the value empty.
After saving this business dimension, you will need to request data reprocessing for reporting dimensions to be populated.