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

[exporter/azuremonitor] Forward net.* attributes to Application Insights #31438

Closed
Soulusions opened this issue Feb 27, 2024 · 3 comments
Closed
Labels

Comments

@Soulusions
Copy link

Component(s)

exporter/azuremonitor

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

I'm currently using the Azure Monitor exporter without much issue outside the outdated semconv attribute mappings, which I was able to fix, but I can't seem to find a way to make the Azure specific Client_* attributes map properly, they're present in the customDimensions under net.country, same with the user_agent, and yet, the ones appearing here are from the collector itself.
As a fair note, I AM pretty new to using otel on a standalone basis and I might just be missing what could be done through a processor.

Describe the solution you'd like

I think a good solution would either be a flag to map the attributes if present, or, as stated above, the use of a processor to remap things properly.

Describe alternatives you've considered

No response

Additional context

Here's a picture of what things look like in application insights:
image
As you can see, every single request is marked as coming from the netherlands, in the datacenter where I just so happen to host the collector. (You can't see it in this screenshot directly, but the customDimensons DOES hold all the data I'd like to be put at the root of the envelopes in their appropriate fields.)

@Soulusions Soulusions added enhancement New feature or request needs triage New item requiring triage labels Feb 27, 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 Apr 29, 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 Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant