This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://learn.microsoft.com/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.
MIT License
5.17k
stars
4.54k
forks
source link
OpenTelemetry Resource Attributes are not exported to Azure Monitor #44257
When I run my application I manage to get data from OpenTelemetry into Azure Monitor, but I have some trouble with the resource attributes that I provide in my setup.
This guide only adds the serivce.name attribute but my understanding is that you can add any custom attribute here, and that it
is not required to be one of the attributes defined in the semconv.
I've found another issue mentioning this, but I'm not sure if it is directly related, as this is in the contrib repository. I can also confirm that the resource attributes are added and logged by using the console exporter.
Is this a limitation in Azure Monitor or maybe a misconfiguration or misunderstanding on my side? I struggle to find any documentation on this, so creating this issue is kind of is my last idea of how to get any further with this problem. :)
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cijothomas @rajkumar-rangaraj @reyang @TimothyMothra @vishweshbankwar.
Library name and version
Azure.Monitor.OpenTelemetry.Exporter
Query/Question
When I run my application I manage to get data from OpenTelemetry into Azure Monitor, but I have some trouble with the resource attributes that I provide in my setup.
This guide only adds the serivce.name attribute but my understanding is that you can add any custom attribute here, and that it is not required to be one of the attributes defined in the semconv.
I've found another issue mentioning this, but I'm not sure if it is directly related, as this is in the contrib repository. I can also confirm that the resource attributes are added and logged by using the console exporter.
Is this a limitation in Azure Monitor or maybe a misconfiguration or misunderstanding on my side? I struggle to find any documentation on this, so creating this issue is kind of is my last idea of how to get any further with this problem. :)
Thanks in advance!
Environment
No response