search

open-telemetry / opentelemetry-collector-contrib

Contrib repository for the OpenTelemetry Collector
https://opentelemetry.io
Apache License 2.0
2.72k stars 2.15k forks source link

Azure Monitor Exporter Role Name differences #31884

Open kylejuliandev opened 3 months ago

kylejuliandev commented 3 months ago

Component(s)

exporter/azuremonitor

Describe the issue you're reporting

Hi,

Not necessarily an issue, more a question in how the Cloud RoleName is generated in the Azure Monitor Collector exporter, versus the .NET Azure.Monitor.OpenTelemetry.Exporter

The collector exporter formats the RoleName as: service_name or service_namespace.service_name (see below)

https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/80ebb76abe215144c0c3314c19e1a767629433cd/exporter/azuremonitorexporter/contracts_utils.go#L34

However, the .NET SDK generates a RoleName with the following: service_name or [service_namespace]/service_name (see ResourceExtensions.cs)

We're migrating away from the in-app SDK to depend on the collector instead, however the inconsistency with RoleName may mean we may need to redo some our queries or alerts

Which is the correct approach?

github-actions[bot] commented 3 months ago

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

github-actions[bot] commented 1 month ago

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.