-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure Monitor Exporter Role Name differences #31884
Comments
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
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: