Applies to: Cost Transparency, Bill of IT, and Hybrid Business Management on TBM Studio 12.8.3 and later
Cloudability cost data can be integrated with other cost data in other Apptio applications, such as Cost Transparency, Hybrid Business Management, and Bill of IT. The integration simplifies setup and maintenance by providing a single point of connecting cloud providers across all Apptio applications.
Step 1 - Initiate the integration and set up the Datalink Cloudability connector
To initiate the integration process and set up the Datalink Cloudabiity connector, see the Datalink Cloudability Connector Guide. This step is required before you can proceed with Step 2.
Step 2 - Set up TBM Studio to ingest Cloudability data
After the Datalink Cloudability connector is set up, use the following the steps to integrate Cloudability-sourced cloud billing data into TBM Studio.
NOTE: ATUM 3.0 columns are mapped by default. Versions 2.0 and 2.1 can be configured, but you must first file a support ticket. ATUM 1.0 is not supported.
- Use Apptio's Datalink Cloudability connector to load Cloudability data. See the Datalink Cloudability Connector Guide.
NOTE: CTF- Cloud component creates separate table each of the cloud providers connected to Cloudability. These are under Cloudability group:
- For AWS: cldy_monthly_aws
- For Azure: cldy_monthly_azure
- For GCP: cldy_monthly_gcp
- The three tables are appended in “CLDY Transform Master Data”, check it out and ensure all the required fields are getting appended.
NOTE: “Row Id” field is unique identifier, add more fields if required to make it unique
- Check out the Cloud Service Provider Master Data table, and remove all appends.
- Update the first formula step to the following formula:
- Clear the formulas in the following columns in the first Formulas step:
- Instance Type
- Platform
- Service Category
- Service Name
- Service Type
- Tower
- Subtower
- Type
- Unit
- Delete the following columns in the first formula step:
- Instance Type Lookup
- Service Category Lookup
- Service Name Lookup
- Service Type Lookup
- Subtower Lookup
- Tower Lookup
- Type Lookup
- Unit Lookup
- (Optional) The following columns aren't required for the integration, but consider removing them from the Cloud Service Provider Master Data table to improve performance; otherwise, skip to the next step:
- From the first Formulas step:
- Amortized Reserved Instance_Cloud Key
- Azure Preprocessed Data Loaded
- Cash-Based Reserved Instance_Cloud Key
- All “Completeness” columns
- CUR Blended Reserved Instance_Cloud Key
- CUR Loaded
- Primary Unit of Measure
- Primary Usage Qty
- Region Code
- RI Allocation Filter
- Reserved Instance Weighing
- All “Validity” columns
- From the second Formulas step:
- Reserved Instance_Cloud Key
- All “Validity” columns
- In the Append step, append CLDY Transform Master Data table into the Cloud Service Provider Master Data table with the following mappings:
- Application =<desired Application dynamic field, if any, otherwise leave blank>
- Business Unit=<desired Business Unit dynamic field, if any, otherwise leave blank>
- Cost =<desired Cost column> OR Base Currency Total Cost if cost is non-USD
- Environment =<desired Environment dynamic field, if any, otherwise leave blank>
- Instance Type =Instance Type
- Invoice Amount =Cost
- IsSharedService =”NO”
- IS CLDY = “Yes”
- Location =<Availability Zone or Region>
- Platform =Platform
- Product =Product
- ProductCode =Product Code
- Provider =Provider
- Provider Region =Region
- Purpose =<desired Purpose dynamic field, if any, otherwise leave blank>
- RecordID =Row ID
- Service Category =Service Category
- Service Name =Service Name
- Service Type =Service Type
- Subtower =SubTower
- Tower =Tower
- UID Metafield =Row ID
- Unit =Unit
- Usage Qty =Effective UsageQuantity
- Check out the Servers Master Data table.
- On the append from the Cloud Servers Transform, update the following column:
- OID Metafield = ITRT_Cloud_Resource_Key Metafield}&&RecordID
- Validate and update allocation strategies as needed.
- Check in your changes.
The Apptio preprocessor will now import Cloudability data and create grouped files with ATUM mappings and specified dynamic fields (if provided) in Apptio S3.