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.

Sign up for GitHub

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

Jump to bottom

[QUERY] Azure.Monitor.OpenTelemetry.AspNetCore - How to write custom dimensions with ILogger? #47594

Open
Leonardo-Ferreira opened this issue Dec 17, 2024 · 3 comments
Open

[QUERY] Azure.Monitor.OpenTelemetry.AspNetCore - How to write custom dimensions with ILogger? #47594

Leonardo-Ferreira opened this issue Dec 17, 2024 · 3 comments
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor - Distro Monitor OpenTelemetry Distro needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@Leonardo-Ferreira
Copy link

Library name and version

Azure.Monitor.OpenTelemetry.AspNetCore 1.3.0-beta.2

Query/Question

using Azure.Monitor.OpenTelemetry.AspNetCore as a "sink" and ILogger, how can I write a log with a custom dimension that will show for that log alone? I don't want the custom dimension to reflect for the all the logs/dependencies/metrics of a given request... just like the classical LogTelemetry.CustomDimensions.Add("specificDimensionA", "value A") ?

Environment

.net 9, latest version
other packages:
OpenTelemetry.Exporter.Console
OpenTelemetry.Extensions.Hosting
OpenTelemetry.Instrumentation.AspNetCore
@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 17, 2024
@cidico
Copy link

cidico commented Dec 17, 2024

I've being trying to do this as well.
Let me know if you find a solution!

@jsquire jsquire added Service Attention Workflow: This issue is responsible by Azure service team. Client This issue points to a problem in the data-plane of the library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Monitor - Distro Monitor OpenTelemetry Distro and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Dec 18, 2024
@github-actions GitHub Actions
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @rajkumar-rangaraj @TimothyMothra.

@AugustoNeves
Copy link

I would also like to know the answer to this question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor - Distro Monitor OpenTelemetry Distro needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jsquire @cidico @Leonardo-Ferreira @AugustoNeves