Setting Up Cost Analytics

To use Commander cost analytics, carry out the following tasks:

  1. Configure the Default Ownership policy, so that ownership is applied to costs. See Cost analytics and ownership below.
  2. (Public cloud only) Retrieve billing data for GCP, AWS and Azure.

    While you can view Cost Analytics without setting up billing data retrieval, the costs that you'll see will be estimates of your public and private cloud expenses. To view accurate information for public cloud accounts, you must retrieve the relevant billing data for these accounts. A message appears at the top of the Cost Analytics page if billing retrieval isn't configured for any managed systems. If actual billing data isn't available, Commander uses the cost model to generate estimates for the Cost Analytics tables.

    GCP: Once billing data retrieval is configured for GCP, estimated costs are replaced with billing data costs in cost analytics. Cost analytics won't include costs for services associated with any billing accounts for which data hasn't been retrieved, so we recommend retrieving billing data for all associated billing accounts.

    For private clouds, the costs shown are based on estimated cost metrics.

  3. (Optional, for upgrades only) If you want to immediately migrate the past 60 days of pre-upgrade billing data, edit the schedule for the database maintenance task.
  4. Grant permissions to Service Portal users who need to view cost analytics.

If you don’t see the costs you expect to see, or if no costs are visible, see Troubleshooting Cost Analytics.

Cost analytics and ownership

For accurate Cost Analytics information, you must assign ownership to services.

To learn how to assign ownership to existing services, see Assigning Ownership to Services. To learn how to configure the ownership policy, see Assigning Service Ownership with Default Ownership Policies.

For VMs that provide service to multiple organizations, you can allocate costs to the organizations that use the service. Adjust the percentage as required, based on usage changes. For more information, see Allocating Service Costs to Multiple Organizations.

How Commander determines ownership of unmanaged public cloud services

When you retrieve public cloud billing data, Commander cost analytics includes costs for types of services it doesn't manage. In order to display accurate cost analytics, Commander assigns an owner to these costs. The order of precedence that Commander uses to determine the ownership of unmanaged services varies for each public cloud. Once ownership information is found in one of these checks, no further ownership checks are made.

For AWS:

  1. Commander first checks the AWS Auto Scaling group that the service belongs to and uses its ownership.
  2. Next, Commander checks the stack that the service belongs to and uses its ownership.
  3. Next, Commander checks the ownership policy to determine the ownership.
  4. AWS billing records don't contain (VPC) Virtual Private Cloud information, so any ownership assigned at the VPC level can't be applied.

For Azure:

  1. Commander first checks the resource group that the service belongs to and uses its ownership.
  2. Next, Commander checks the ownership policy to determine the ownership.

For GCP:

  • GCP provides costs at the project level, not at the level of the specific resource. Because Commander doesn't allow you to manually assign ownership to GCP projects, you must configure an ownership policy to assign ownership. Through the ownership policy, you can assign ownership at the level of the managed system, organization, folder, project, region or zone.