Open markrendle opened 4 months ago
Pinging code owners:
receiver/azureeventhub: @atoulme @djaglowski @cparkins
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue was approved of and suggested by a code owner in the linked PR, removing needs triage
.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Component(s)
receiver/azureeventhub
Is your feature request related to a problem? Please describe.
When ingesting Azure Resource Logs from Azure Event Hubs, the property names are arbitrary, presumably chosen by each team. In some cases the property names for the same semantic value differ between logs from the same Azure service, e.g.
clientIp
andclientIP
. This makes querying and processing saved logs unnecessarily difficult.Describe the solution you'd like
Where an OTel Semantic Convention exists to describe a property, change the property name to the SemConv equivalent in the translated log record, e.g.
clientIp
andclientIP
would both becomeclient.address
.Properties that can be mapped like this may be "promoted" to top-level attributes on the translated log record; other properties can remain in the nested
properties
map.Describe alternatives you've considered
No response
Additional context
The initial work, covering Azure App Service and Azure Front Door, is already done in PR #32486