Skip to content

Convert more standard OTel properties to Azure Monitor conventions #40598

Open
@mmarczell-graphisoft

Description

@mmarczell-graphisoft

Component(s)

exporter/azuremonitor

Is your feature request related to a problem? Please describe.

Our usecase is a mobile application instrumented with the Embrace SDK:

sending OTel data to our own Collector which then exports to Azure Application Insights.

This SDK fills some of the standard OTel properties but not all of them appear on the AppInsights web UI.

Describe the solution you'd like

The Azure Monitor exporter already performs some mapping of property names as documented in https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/azuremonitorexporter/README.md.

It should additionally perform the following mapping:

Application Insights property OpenTelemetry attribute
application_Version service.version
client_OS os.name concatenated with os.version
client_Model device.manufacturer
client_Type device.model.identifier

It looks like it already performs the below mapping in https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/azuremonitorexporter/contracts_utils.go - this should be documented:

Application Insights property OpenTelemetry attribute
cloud_RoleName service.name

I would like to send a PR, but please respond if the above is not correct.

Describe alternatives you've considered

I could fill out these AppInsights specific fields manually in the mobile app but that is the wrong architectural place for that code.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions