Wiktor Kopec

Possibly related https://github.com/dotnet/diagnostics/issues/3479

This is a very reasonable feature, but we have to make sure we don't regress https://github.com/dotnet/dotnet-monitor/issues/923. I.e. once an interval for a provider is established in one scenario such as...

> @wiktork So, there'd be no way to split this and have different intervals for different streams? ie, one interval for the trace call and another for the live metrics?...

> I think the ask here is to allow specifying these per provider so that all collection mechanism are not artificially locked into the same interval. For example, if the...

Previously reported issues: #2761, #2760 Are you scraping the metrics endpoint with Prometheus, or do you just want metrics for multiple processes?

https://github.com/dotnet/samples/tree/main/core/profiling/stacksampling

Tentative design for this will be to create additional configuration with a default pattern that can be applied to each artifact type. This would include our typical substitution tokens, such...

Another possible approach would be to enforce these limits on a per process basis rather than globally. I think this is a reasonable feature. Some considerations: - Certain operations (dumps,...

Enabled through DOTNET_DefaultDiagnosticPortSuspend for regular scenarios. Also consider [ds-router](https://github.com/dotnet/diagnostics/tree/main/src/Tools/dotnet-dsrouter) scenarios owned by @lateralusX.

This is likely a fallout of https://github.com/dotnet/aspnetcore/pull/22376