Skip to content

[feature request] Azure Monitor: Metrics collection interval #2581

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

Open
vRune4 opened this issue Mar 4, 2025 · 0 comments
Open

[feature request] Azure Monitor: Metrics collection interval #2581

vRune4 opened this issue Mar 4, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@vRune4
Copy link

vRune4 commented Mar 4, 2025

Component

Azure.Monitor.OpenTelemetry.AspNetCore

Is your feature request related to a problem?

I am troubleshooting thread starvation issues and I am currently running dotnet-counters in a console trying to capture this data. I have not tried dotnet-counters collect yet since my first thought was to try to collect this information directly to a Azure Log Workspace.

I notice that the PeriodicExportingMetricReader() constructor has an exportIntervalMilliseconds parameter. It would be neat if I could get to that somehow. (I need a sample at least every second)

What is the expected behavior?

A configuration setting for sample interval that allows me to harvest counters more often. Ideally... I need the thread-queue length and thread-count counters for now.

Which alternative solutions or features have you considered?

dotnet-counters collect

Additional context

My initialization code:

builder.Services.AddOpenTelemetry()
		.UseAzureMonitor(opt => { opt.Credential = credential; opt.ConnectionString = appInsightsConnectionString; })
		.WithMetrics(m => { m.AddRuntimeInstrumentation(); });
@vRune4 vRune4 added the enhancement New feature or request label Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant