On the Views page, you can view, edit or create new views to use across your organisation. You can use a single dimension, eg account or tag key, or use multiple dimensions to create a single view. It all depends on your account setup, tagging hygiene and organisational needs.

Tip: You will need to be an Administrator to create new views. It will take about an hour for rules to be reflected on the Home page & in the Global Filters.

To create your first view

Click New View on the Views page.

Give your new view a name. We recommend setting up views to match Cost Centres, Projects, Environments and other things that teams within your organisation need help visualising.

Choose which method you want to use in setting up your new view. a single dimension like Tag or Account is the easiest, but if your tagging hygiene isn't great, you'll end up with a lot of unallocated costs. You can check your tagging in the Explore Data section of Stax and choose a tag from there.

Unless you choose a combination of dimensions, we will then ask you if you want to do quick mapping where we auto-detect all the tag values for the given tag key and auto-create segments for each or whether you want to manually map the variants to segments.

We will then go through your accounts, detect the values and give you something like this-

It can take 4+ hours for us to process your data and populate the views across Stax.

Need to create a Multi-dimensional view? 

We recommend that you read the article here.

The first step is the same, but instead of selecting a single dimension, make sure you select A Combination of Dimensions.

You'll then need to think about how we can create rules to split your data the way your organisation needs to see it. 

Many organisations have multiple accounts for different purposes. 

Each project or team may have separate accounts for development vs production. In this case, you'd want to use AWS Accounts and create a segment for each team. The same might be true for projects. 

If your tagging isn't great, often using a combination of dimensions is a good way to go.

Once you select the dimension you want to start with, you'll need to create segments to which you'll allocate your resources.

Then you should add the dimensions, whether it's starting with tags, accounts, products or even ARNs for those hard-to-tag items!

All you need to remember is that the list of rules works like a funnel. The first rule is the top priority. If there are resources that don't fit any of the rules, they'll end up showing as 'unallocated' when you check your views.

You can click the up and down arrows to re-order your rules and add or remove rules any time. Do keep in mind that the charts and tables don't update in real-time, so please allow us time to re-calculate everything!

Rule dimensions:

AWS Resource Tags

  • Add tag keys/values to rules, to specify tagged resources to be allocated to a segment.
  • Tags entered are case sensitive
  • Use wildcards – e.g. Tag value = division and tag key = API* would allocate resources with the Division tag with any key that starts with ‘API’ to that segment.

ARN

  • Certain resources can be hard to tag.
  • Use the ARN dimension dimension to allocate metrics for specific AWS resources to a segment. 

Account

  • Use the Account dimension to select AWS accounts to allocate metrics to a segment. You can add other dimensions to the rule, such as AWS service or tags, to narrow down to metrics within an account.
  • If you don’t select an account at all, the rule will use all accounts.

Master Account

  • Use the Master Account dimension to split your view by master payer account. You can add other dimensions to the rule, such as AWS service or tags, to narrow down to metrics within your master accounts.

Product

  • Use the Product column to allocate metrics for specific AWS services to a segment. E.g. if you know that only Project Pikachu is using Lambda, create a rule to allocate all Lambda costs to Pikachu.

Region

  • Use the Region dimension to allocate metrics for specific AWS regions to a segment. E.g. if you know that only Project Pikachu is using US-West, create a rule to allocate all US-West costs to Pikachu.

Usage Code

  • Use the Usage Code dimension to allocate metrics for specific usage codes to a segment. This could be data_transfer, snapshot_storage , instance_usage, etc. This would be a great way to find out how much your snapshots for a specific project, service, team, etc. are costing.

Unallocated metrics:

  • Any metrics not captured in the rules in the table will automatically be added to an ‘Unallocated’ category which will display in the drop down Global Filters, and on the Cost Breakdown table.

Did this answer your question?