CloudSpend Tag Profile

A Tag Profile provide customized labels that group user-defined parameters such as resourceLocation, service, resource, resourceGroup, meter category, and meter subcategory. It allows you to manage your cloud costs efficiently. There are both user-defined tags and system-generated (AWS, Azure, or GCP) tags. Each tag has a unique value and you can combine multiple tags using AND/OR conditions while creating a tag profile. 

The CloudSpend AWS cost supports Parquet and GZIP file formats of legacy AWS Cost and Usage Reports. For cost accounts parsed from the Parquet format report, the user-defined tags with camel case, colon, and hyphen will be replaced with an underscore and follow lower casing.

See the below table for examples:

Tag name in GZIP file type Tag name in Parquet file type
autoscaling:groupName autoscaling_group_name
cloudformation:id cloudformation_id
CreatedBy created_by
Environment-type environment_type

The system-generated tags will not have any changes.

Benefits of a Tag Profile

Some of the key benefits of a Tag Profile include:

  • Managing cloud data in an easy and efficient manner.
  • Breaking down and analyzing cloud costs from a bird's-eye view.
  • Group, filter, and understand cloud costs using different parameters like resourceLocation, service, accounts, resource types, and meter category.
  • Reuse and combine two or more tags to create a Business Unit or Budget to reuse in the future.

System tags

Click on each tab below to view the system-generated tags.

System-generated tags for AWS

CloudSpend provides the following system-generated tags for AWS:

  • usageType
  • operationType
  • usageInfo
  • serviceName
  • dataTransferType
  • instanceType
  • usageSubType
  • availabilityZone
  • regionName

System-generated tags for Azure

CloudSpend provides the following system-generated tags for Azure:

  • frequency
  • chargeType
  • consumedService
  • meterCategory
  • meterName
  • meterSubCategory
  • pricingModel
  • resourceLocation
  • resourceType
  • product
  • resourceGroup
The value for the resourceGroup tag is the resource group name and it will always be in lowercase. For example, say you have a resource group called Production_Environment in Azure. Here, the tag value for the resourceGroup will be production_environment.

System-generated tags for GCP

CloudSpend provides the following system-generated tags for GCP:

  • costType
  • skuName
  • serviceName
  • serviceName
  • creditType
  • regionName
  • transactionType
  • zone
  • adjustmentType
  • adjustmentMode

Creating a Tag Profile

To create a Tag Profile:

  1. Go to the CloudSpend console.
  2. From the left navigation pane, select Admin.
  3. Click and expand the Profiles tab.
  4. Select Tag Profile to see a list of all the existing tag profiles created.
  5. Click Add Tag Profile to add a new tag profile.
  6. In the Tag Profile dialog box, enter the following details:

    Field Description
     Tag Key  The tag name
     Cost Account  The desired cost account (selected from the drop-down list)
     Tag Value  The applicable tag for filtering
     Color  The preferred Tag Profile color
    Tag Profile
  7. Click Save.

Editing a Tag Profile

To edit a Tag Profile:

  1. Go to the CloudSpend console.
  2. From the left navigation pane, select Admin.
  3. Click and expand the Profiles tab.
  4. Select Tag Profile to see a list of all the existing tag profiles created.
  5. Click the hamburger icon corresponding to the tag profile you wish to edit.
  6. Click Edit and edit the necessary fields.
  7. Click Save to save the changes.

Deleting a Tag Profile

To delete a Tag Profile:

  1. Follow steps 1-5 from the Editing a Tag Profile section.
  2. Click Delete to delete the tag profile.

Use cases

The following examples explain different scenarios where tags are used with the AND/OR conditions while creating a Tag Profile.

Example 1

You want to filter cost data using the resourceLocation tag key for an account of your choice. For instance, let's use the resourceLocation:East US tag and resourceLocation:West US tag. Here, we use the OR condition and enter the tags. Thus, we can get data for the resources present in the East US OR West US region.

Tag Profile Example OR condition

Example 2

Say you want to filter compute service data with two tags using the DataTransferOut tag key for an account of your preference. In this scenario, let's use the meterName:Standard Data Transfer Out tag and consumedService:microsoft.compute tag. Here, the AND condition is used, so that the filter is applied based on both the meterName and consumedService tags.

AND condition example

Example 3

You now want to add multiple tags for an account of your preference using both the AND/OR conditions. For instance, let's use the resourceLocation:East US tag, resourceLocation:EU West tag and the meterCategory:Virtual Machines tag with parenthesis to group and retrieve the data according to the logical operations order.

In this case, we enter these tags as: (resourceLocation:East US OR resourceLocation:EU West) AND meterCategory:Virtual Machines. In this example, the application will display the data for either resourceLocation:East US or resourceLocation:EU West and data for meterCategory:Virtual Machines for the applicable account.

Combination scenarios

Invalid expressions scenarios

While creating a Tag Profile, invalid expressions can occur if the data entry is incomplete, if operations are missing, or if inputs are invalid. The below examples of invalid expressions can occur in a logical expression while using Tag Profiles in CloudSpend:

  • No logical operation (OR/AND)
    • e.g.: Virtual Machines, East US
  • No opening or closing braces
    • e.g.: microsoft.compute) AND East US


Related topics
Top
Home » Tag Profile