This change is a follow up to #66 and introduces two fixes.
@brian-brazil as you pointed out during the review of that change, it is important to differentiate
between meta-data coming from Azure Monitor and tags defined by our users, as they can clash.
My recommendation was to prefix tags in order to do so, however this change never made it to the final PR. I am proposing this PR to introduce these prefixes.
Also, I went ahead and removed the invalid label prefix check as that has become obsolete with current change.
We are generating the resource_name label from AzureResource.Name. This can cause inconsistency when we try to map metrics against azure_resource_info, as certain resource types contain a sub resource name that is used in resource_name. To overcome this limitation this change proposes to overwrite the resource_name label the same way we do for all the other metrics.
This change is a follow up to #66 and introduces two fixes.
@brian-brazil as you pointed out during the review of that change, it is important to differentiate between meta-data coming from Azure Monitor and tags defined by our users, as they can clash. My recommendation was to prefix tags in order to do so, however this change never made it to the final PR. I am proposing this PR to introduce these prefixes. Also, I went ahead and removed the invalid label prefix check as that has become obsolete with current change.
We are generating the
resource_name
label fromAzureResource.Name
. This can cause inconsistency when we try to map metrics againstazure_resource_info
, as certain resource types contain a sub resource name that is used inresource_name
. To overcome this limitation this change proposes to overwrite theresource_name
label the same way we do for all the other metrics.