-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Sampling affects the accuracy of performance metrics #36705
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I assume thats something azure monitoring specific? Not sure what metrics azure expects. But you may want to generate your metrics before applying some kind of sampling. You may want to look into the |
Yes, these are AzureMonitor-specific metrics.
I'm too lazy and would prefer having it out of the box. :) At least it is already available in Application Insights SDK and its successor For example, Application Insights SDK has an AutocollectedMetricsExtraction which produces metrics similar to the one below:
I guess these metrics are then used for building and rendering the Application Map and other GUI. I also thinking it doesn't depend on #34272 as I initially thought. |
Component(s)
exporter/azuremonitor
Describe the issue you're reporting
I'd like to see correct numbers of operations/calls on Application Map and Performance/Failure blades even if most of telemetry was aggressively sampled out by collector.
E.g. an application is handing 1000 requests and makes 1000 SQL queries to accomplish that. OTEL Collector is using the following sampling configuration to retain only 1% of telemetry:
As an outcome, the Application Map is showing only 10 operations which were sampled in even if there was much more (1000 in my example).
Both Application Insights SDK for .NET and
Azure.Monitor.OpenTelemetry.Exporter
are providing that capability. Could the exporter/azuremonitor benefit from #34272 to provide similar experience?The text was updated successfully, but these errors were encountered: