Documentation

FOCUS Integration

Load any FOCUS formatted file into Ternary

Overview

Provide Ternary with a billing file that aligns to the FOCUS schema which will be made available to view in our application. This is done by providing us access to an AWS or GCP storage bucket.

FOCUS File Requirements

There are currently a set of required, recommended and optional columns in a focus file which are as follows, any dimension columns not in the below list will be available in our reporting engine when viewing the generic focus bill, however they will not be included in the multi-cloud data.

Required Columns

  • BilledCost
  • BillingAccountId
  • BillingAccountName
  • BillingCurrency
  • BillingPeriodStart
  • BillingPeriodEnd
  • ChargeCategory
  • ChargeClass
  • ChargeDescription
  • ChargePeriodStart
  • ChargePeriodEnd
  • ContractedCost
  • EffectiveCost
  • InvoiceIssuerName
  • ListCost
  • PricingQuantity
  • PricingUnit
  • ProviderName
  • PublisherName
  • ServiceCategory
  • ServiceName

Recommended Columns

  • AvailabilityZone
  • ChargeFrequency

Conditional Columns

  • CommitmentDiscountCategory
  • CommitmentDiscountId
  • CommitmentDiscountName
  • CommitmentDiscountStatus
  • CommitmentDiscountType
  • ConsumedQuantity
  • ConsumedUnit
  • ContractedCost
  • ContractedUnitPrice
  • ListUnitPrice
  • PricingCategory
  • RegionId
  • RegionName
  • ResourceId
  • ResourceName
  • ResourceType
  • SkuId
  • SkuPriceId
  • SubAccountId
  • SubAccountName
  • Tags

Setup

Start by navigation to the Admin section of the left side navigation, then choose "New Integration" in the upper right corner. Then select the option for "Generic FOCUS Bill"

On the configuration page you will need to provide a name which can be any text value. Along with the URI location of the folder/file. You can paste the full path into the text box and we will automatically parse the necessary information including the vendor (AWS/GCP).

After you paste the storage URI, you will be shown the necessary IAM permissions needed to provide Ternary access to read the data. This needs to be added to the existing permission's for us to collect the detailed billing data. note if you are putting these files in the same AWS bucket that your CUR (cost and usage report) we do not need any additional permissions, however they must be in a separate folder within the same bucket.

Technical Details

  • We will process all files in the provided location which will stay up to date. If you intend to give us multiple files for a single billing period, be sure to delete older versions to prevent from having duplicated data.
  • If you delete a file, we will also remove the associated data in Ternary.