You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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?
The text was updated successfully, but these errors were encountered:
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.
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
orservice_namespace.service_name
(see below)opentelemetry-collector-contrib/exporter/azuremonitorexporter/contracts_utils.go
Line 34 in 80ebb76
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?
The text was updated successfully, but these errors were encountered: