Automated env allocation visibility

​

Prerequisites:

• If you have an AWS provider connected to Costory, you enabled in Cost Allocation tags AWS UI all the tags available.
• If you’re using the same Kubernetes cluster for all your environments, you have a way to identify the environment of the pod using a namespace / or a label attached to the pod.
• You identified which marketplace purchases are required for your production environment.

​

Output:

• You can compute your cost per environment either using only labels, or using a virtual dimension.
• You can schedule monthly reports to share with your team to monitor the cost of each environment.
• Your Digest will surface the cost changes for each environment.

​

Steps:

1

Step 1: Automatically ingest all the env related labels available in your billing data

As soon as you will connect your billing data to Costory, we will analyze all the available labels and find the ones that are related to environemnts.Automatic feature engineering includes:

• Merge columns from multiple sources into a single label: k8s_label_env with env and environment, environnment…
• Rename values to standardize naming across providers: stg-> staging, dev-> development, prod-> production…

2

Step 2: Create a virtual dimension to allocate the leftover costs

Some of your costs might not be allocated using those labels:

• either because they can’t (network costs, DataDog, )
• or because they would require an additional split (for example a marketplace purchase used in both prod and staging) that you need to share.

To fill this gap, you can create a virtual dimension to allocate those costs:

3

Step 3: Create a report to visualize the cost allocation

Now that you have a way to allocate this opens a lot of possibilities:

• Share a report with your exec team: here
• Calculate marginal cost of your prod app using an external metric: here