-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Open
Labels
ClientThis issue is related to a non-management packageThis issue is related to a non-management packageMonitor - DistroMonitor OpenTelemetry DistroMonitor OpenTelemetry DistroService AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Description
Library name and version
Azure.Monitor.OpenTelemetry.AspNetCore 1.4.0-beta.1
Describe the bug
If the Live Metrics blade is viewed in Application Insights, an ArgumentOutOfRangeException is thrown (and caught) in the Azure Monitor SDK.
Expected behavior
No exception thrown for known telemetry types.
Actual behavior
An Unsupported TelemetryType: 'Event' ArgumentOutOfRangeException is thrown in Azure.Monitor.OpenTelemetry.LiveMetrics.Internals.Filtering.DocumentStream.CreateFilters
This exception is caught and ignored, but seems to indicate unimplemented functionality in the Azure Monitor SDK.
Call stack
Azure.Monitor.OpenTelemetry.Exporter.dll!Azure.Monitor.OpenTelemetry.LiveMetrics.Internals.Filtering.DocumentStream.CreateFilters(out Azure.Monitor.OpenTelemetry.LiveMetrics.Models.CollectionConfigurationError[] errors) Line 131 C#
Azure.Monitor.OpenTelemetry.Exporter.dll!Azure.Monitor.OpenTelemetry.LiveMetrics.Internals.Filtering.DocumentStream.DocumentStream(Azure.Monitor.OpenTelemetry.LiveMetrics.Models.DocumentStreamInfo info, out Azure.Monitor.OpenTelemetry.LiveMetrics.Models.CollectionConfigurationError[] errors, float? initialRequestQuota, float? initialDependencyQuota, float? initialExceptionQuota, float? initialEventQuota, float? initialTraceQuota, float? maxRequestQuota, float? maxDependencyQuota, float? maxExceptionQuota, float? maxEventQuota, float? maxTraceQuota, float? quotaAccrualRatePerSec) Line 40 C#
Azure.Monitor.OpenTelemetry.Exporter.dll!Azure.Monitor.OpenTelemetry.LiveMetrics.Internals.Filtering.CollectionConfiguration.CreateDocumentStreams(System.Collections.Generic.IEnumerable<Azure.Monitor.OpenTelemetry.LiveMetrics.Internals.Filtering.DocumentStream> previousDocumentStreams, out Azure.Monitor.OpenTelemetry.LiveMetrics.Models.CollectionConfigurationError[] errors) Line 113 C#
Azure.Monitor.OpenTelemetry.Exporter.dll!Azure.Monitor.OpenTelemetry.LiveMetrics.Internals.Filtering.CollectionConfiguration.CollectionConfiguration(Azure.Monitor.OpenTelemetry.LiveMetrics.Models.CollectionConfigurationInfo info, out Azure.Monitor.OpenTelemetry.LiveMetrics.Models.CollectionConfigurationError[] errors, System.Collections.Generic.IEnumerable<Azure.Monitor.OpenTelemetry.LiveMetrics.Internals.Filtering.DocumentStream> previousDocumentStreams) Line 45 C#
Azure.Monitor.OpenTelemetry.Exporter.dll!Azure.Monitor.OpenTelemetry.LiveMetrics.Internals.LiveMetricsClientManager.RefreshConfigurationOnEtagChange(Azure.Monitor.OpenTelemetry.LiveMetrics.Internals.QuickPulseResponse response) Line 410 C#
Azure.Monitor.OpenTelemetry.Exporter.dll!Azure.Monitor.OpenTelemetry.LiveMetrics.Internals.LiveMetricsClientManager.OnPing() Line 364 C#
Azure.Monitor.OpenTelemetry.Exporter.dll!Azure.Monitor.OpenTelemetry.LiveMetrics.Internals.LiveMetricsClientManager.Run() Line 500 C#
Reproduction Steps
- Install and configure Azure.Monitor.OpenTelemetry.AspNetCore as per https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-dotnet-migrate?tabs=aspnetcore#enable-opentelemetry
- Set up a Connection String for an Application Insights instance
- Run your application under the VS debugger
- In the Application Insights instance, open the Live Metrics blade
- An
Unsupported TelemetryType: 'Event'ArgumentOutOfRangeExceptionis thrown inAzure.Monitor.OpenTelemetry.LiveMetrics.Internals.Filtering.DocumentStream.CreateFilters
Environment
Windows 11 25H2
❯ dotnet --info
.NET SDK:
Version: 9.0.306
Commit: cc9947ca66
Workload version: 9.0.300-manifests.4f997495
MSBuild version: 17.14.28+09c1be848
Runtime Environment:
OS Name: Windows
OS Version: 10.0.26200
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\9.0.306\
.NET workloads installed:
[android]
Installation Source: SDK 9.0.300, VS 17.14.36623.8
Manifest Version: 35.0.105/9.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.sdk.android\35.0.105\WorkloadManifest.json
Install Type: Msi
[ios]
Installation Source: SDK 9.0.300
Manifest Version: 26.0.9752/9.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.sdk.ios\26.0.9752\WorkloadManifest.json
Install Type: Msi
Configured to use loose manifests when installing new manifests.
Host:
Version: 9.0.10
Architecture: x64
Commit: e1f19886fe
.NET SDKs installed:
8.0.415 [C:\Program Files\dotnet\sdk]
9.0.111 [C:\Program Files\dotnet\sdk]
9.0.205 [C:\Program Files\dotnet\sdk]
9.0.306 [C:\Program Files\dotnet\sdk]
Metadata
Metadata
Assignees
Labels
ClientThis issue is related to a non-management packageThis issue is related to a non-management packageMonitor - DistroMonitor OpenTelemetry DistroMonitor OpenTelemetry DistroService AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that