How to group resources into Attributions, and then use those Attributions in your Cloud Reports.
Attributions are a flexible way to group resources and their associated costs, helping you understand the cloud costs and relate them to the business in your Cloud Reports.
You may have various components of your application(s) spread across different projects, using different services. Attributions allow you to combine everything into something coherent.
Required Permissions: Cloud Analytics
Creating an Attribution
Select Analytics from the top menu and then select Attributions to access your attributions:
A screenshot of the Attributions screen
To create a new attribution, select the NEW ATTRIBUTION button.
Next, you will be taken to an attribution creation page, where you will configure its conditions and settings.
To start, give your Attribution a name that gives some context. In our example, we'll be creating attributions to group costs for different teams: production, dev, and ops.
If you want to give even more context to your Attribution, you may give it a description by clicking on the icon at the far-right end of the text box.
Now it's time to configure the conditions, or the criteria, which will determine what falls under your Attribution. You have the option to either set as meet "ALL" or "ANY" of the conditions. This will switch between "AND" to "OR" relations.
A screenshot showing the location of the items listed above
You will have every cloud billing dimension to choose from; as well as any custom, project, and system labels. Select the field(s) you'd like to include as part of your Attribution from the dropdown:
A screenshot showing the dropdown menu
From there, filter your selections either by keyword, exclusion, or regular expression just as you would do in Cloud Analytics Reports. Continuing our example from above, let's filter for projects which the production team uses.
A screenshot showing the Filter Projects form
Finally, click "Save" to apply the filter on your condition.
Once you've set a condition, a quick preview will appear showing your attribution's costs over the last 30 days. This will continue to update as you add more conditions. This way, you can easily validate the conditions of your attribution.
Using our example from above, we will also create similar attributions for dev and ops teams.
You should not set multiple separate conditions with the same field — unless there is an exclusion set up in one of those conditions.
Advanced Attribution Options
Once attributions are configured you will have some additional options in the '3-dot' menu to the right of the list:
A screenshot of the attribution list with a 3-dot menu on each line
As the owner of an attribution you will see several option:
A screenshot of the 3-dot menu options
Subscribe to daily digest
Subscribing to a daily digest will send you a daily update showing you month to date cost and run rate for the scope of your attribution.
Grant additional permissions to other users of the CMP or transfer ownership
Remove the attribution from the CMP
In the settings panel you can enable Anomaly Detection for the scope defined by your attribution.
A screenshot of the Attributions Settings panel
By enabling this monitor, the CMP will monitor the scope defined in your attribution for Cost anomalies.
For example, let's say you create an attribution that is filtered to a single or set of SKUs. You would be alerted to anomalies that occur only in that set of objects (as opposed to at the scope of your entire spend per cloud).