Is your change request related to a problem? Please describe.
I'm working on the Azure Event Hubs receiver in Collector Contrib to translate Azure Resource Log property names and Metric to SemConv. One of the Resource Log types comes from Azure Front Door's CDN Access Log, and includes two CDN-specific attributes:
pop: the Point of Presence, e.g. LON
cacheStatus: e.g. HIT or MISS
If there are other CDN solutions that can be monitored via a Collector one might expect these to be common attributes across multiple implementations.
Describe the solution you'd like
A top-level cdn namespace for CDN attributes, with e.g.:
cdn.pop or cdn.point_of_presence for the POP
cdn.cache_status with HIT or MISS as possible values
Describe alternatives you've considered
I considered using cloud.region for the pop attributes, but
Area(s)
area:new
Is your change request related to a problem? Please describe.
I'm working on the Azure Event Hubs receiver in Collector Contrib to translate Azure Resource Log property names and Metric to SemConv. One of the Resource Log types comes from Azure Front Door's CDN Access Log, and includes two CDN-specific attributes:
pop
: the Point of Presence, e.g. LONcacheStatus
: e.g. HIT or MISSIf there are other CDN solutions that can be monitored via a Collector one might expect these to be common attributes across multiple implementations.
Describe the solution you'd like
A top-level
cdn
namespace for CDN attributes, with e.g.:cdn.pop
orcdn.point_of_presence
for the POPcdn.cache_status
withHIT
orMISS
as possible valuesDescribe alternatives you've considered
I considered using
cloud.region
for thepop
attributes, butcacheStatus
Additional context
No response