Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Azure Monitor OTel Exporter Missing Dimensions [BUG]
See original GitHub issueLibrary name and version
Azure.Monitor.OpenTelemetry.Exporter 1.0.0-beta.4
Describe the bug
We’ve had Azure.Monitor.OpenTelemetry.Exporter in Prod for over a week now, and it’s working very well. I did notice that dimensions emitted from our OTel instruments aren’t making it to Azure Monitor – they do show up in Jarvis, as well as on the Console exporter, so we know they’re being emitted. I confirmed this by making a Sample app that emits a histogram metric every ~1.5 seconds or so with one dimension, and it’s not selectable as a split on Azure Monitor:
Expected behavior
Dimensions show up.
Actual behavior
Dimensions don’t show up.
Reproduction Steps
Set up a minimal .NET app emitting Histogram<double> metrics via a Meter, upload it to Application Insights via the library. Then, in the Metrics tab on Portal, as above, observe that you cannot split by dimension.
@TimothyMothra tagged per request.
Environment
No response
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@reynoldsa - Please check this https://learn.microsoft.com/en-us/azure/azure-monitor/app/tutorial-asp-net-custom-metrics#multi-dimensional-metrics
My bad then, thanks for checking on it and for the information 😄