-
Notifications
You must be signed in to change notification settings - Fork 119
TrackMetric only works sometimes when aggregating #628
Comments
@Cooke Metrics are not subject to sampling, so sampling cannot explain the issue. How do you validate that metrics are missing? Its possible are there is a latency before which they show up in portal. Can you verify if local VisualStudio is also showing this missing behavior. ? |
@cijothomas I validate they are missing by not showing up in the portal, and by not seeing any related output in the debug log. It is not possible that this is due to latency since I have a workaround that seems to work 100% and for which I can see the related metrics being present in the portal. What do you mean with local VisualStudio? |
Can you share a small repro for us to dig deeper into this? It's hard to investigate without repro app. Thanks for your time! @Cooke |
@cijothomas Maybe later, too little time now. I just wanted to let you know and share my work around. Thank you for your time and nice service! |
@Cooke Okay. The latest SDK has built-in support for aggregated metrics! It'd be awesome if you can give it a try! |
Closing this for now as no action pending from SDK. Thanks! |
Repro Steps
Actual Behavior
Some of none of the metrics are collected and shown in the portal.
Expected Behavior
All of the metrics are collected (or skipped due to sampling).
Work around
Make sure to explicitly set MetricTelemetry.Context.Operation.Name before calling TelemetryClient.TrackMetric
Version Info
SDK Version : 2.2.1
.NET Version : 2.1.2
How Application was onboarded with SDK(VisualStudio/StatusMonitor/Azure Extension) : Nuget/custom
OS : Win10 x64
Hosting Info (IIS/Azure WebApps/ etc) : console, kestrel
The text was updated successfully, but these errors were encountered: