Tag naming conventions in FlexReports

Products

• CloudHealth

Issue/Introduction

If there is a unique tag, for example 'ServiceName' ('S' and 'N' are in caps), then FlexReports will present the tag as 'servicename' (all lower case).

Resolution

Note that non-duplicate Tags are shown as lowercase. If a duplicate Tag with different case is added to the CUR in a future bill, logic will be applied by inserting “1”. 

Regarding the AWS Cost and Usage Report (CUR), the insertion of “1” after a capital letter happens only if there is a duplicate Tag of different case in the AWS CUR. 

For instance, if “ServiceName” and “servicename” both exist in the same CUR, then:

• “ServiceName” will be "s1ervicen1ame"
•  “servicename” will be “servicename”

Otherwise if there is no duplication, it simply is shown as-is. 

This naming convention applies only for Tags in AWS CUR, where the Tags are raw Columns in the Dataset. 
For Azure and GCP Datasets, the Tags (or Labels) are extracted from the raw JSON column in the Dataset. 
Those are simply converted to lower-case, with leading & trailing spaces removed.