Tag management in Flexreport when there is no duplication of tag

Products

• CloudHealth

Issue/Introduction

If there is a unique tag, for e.g. 'ServiceName' ('S' and 'N' are in caps), then the FlexReport is showing the tag 'servicename' (all lower case). No duplicate tags present for this scenario.

Environment

AWS, Azure, GCP

Resolution

Non-duplicate Tags are shown as lowercase. This is to ensure consistency if a duplicate Tag with different case is added to the CUR in a future bill, triggering the above logic of inserting “1” 

This is firstly done because SQL is a case-insensitive language. And the Case does not matter in the FlexQuery SQL Input. But the FlexReport, Platform would be unable to merge Tag's raw Columns from the CUR, as we are not sure if the Customer wants to or not on a per Tag basis.

In the case of AWS CUR, the insertion of “1” after a capital letter happens only if there is a duplicate Tag of different case in the AWS CUR. 

Like 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.