Skip to content
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

Closed
kylejuliandev opened this issue Mar 20, 2024 · 3 comments
Closed

Azure Monitor Exporter Role Name differences #31884

kylejuliandev opened this issue Mar 20, 2024 · 3 comments

Comments

@kylejuliandev
Copy link

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)

cloudRole = serviceNamespace.Str() + "." + cloudRole

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?

@kylejuliandev kylejuliandev added the needs triage New item requiring triage label Mar 20, 2024
Copy link
Contributor

Pinging code owners:

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

Copy link
Contributor

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.

@github-actions github-actions bot added the Stale label May 20, 2024
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant