.NET 10 meter and instrument tags are empty

[jander-msft]

Functional test is failing when .NET Monitor 10 targets a .NET 10 app producing tags on meters and instruments. This same test passes when .NET Monitor 10 targets a .NET 9 or .NET 8 app, thus indicating this is a regression in .NET 10 itself.

Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests.LiveMetricsTests.TestSystemDiagnosticsMetrics_MeterInstrumentTags​
Error:
Assert.Equal() Failure: Strings differ
Expected: "mKey1=mValue1"
Actual: null

Stack trace:
at Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests.LiveMetricsTests.<>c__DisplayClass8_0.<<TestSystemDiagnosticsMetrics_MeterInstrumentTags>b__0>d.MoveNext() in //src/Tests/Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests/LiveMetricsTests.cs:line 422
--- End of stack trace from previous location ---
at Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests.Runners.ScenarioRunner.<>c__DisplayClass0_0.<b__0>d.MoveNext() in //src/Tests/Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests/Runners/ScenarioRunner.cs:line 92
--- End of stack trace from previous location ---
at Microsoft.Diagnostics.Monitoring.TestCommon.Runners.AppRunnerExtensions.ExecuteAsync(AppRunner runner, Func1 func) in /_/src/Tests/Microsoft.Diagnostics.Monitoring.TestCommon/Runners/AppRunnerExtensions.cs:line 32 at Microsoft.Diagnostics.Monitoring.TestCommon.Runners.AppRunnerExtensions.ExecuteAsync(AppRunner runner, Func1 func) in //src/Tests/Microsoft.Diagnostics.Monitoring.TestCommon/Runners/AppRunnerExtensions.cs:line 46
at Microsoft.Diagnostics.Monitoring.TestCommon.Runners.AppRunnerExtensions.ExecuteAsync(AppRunner runner, Func1 func) in /_/src/Tests/Microsoft.Diagnostics.Monitoring.TestCommon/Runners/AppRunnerExtensions.cs:line 50 at Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests.Runners.ScenarioRunner.SingleTarget(ITestOutputHelper outputHelper, IHttpClientFactory httpClientFactory, DiagnosticPortConnectionMode mode, String scenarioName, Func3 appValidate, Func3 postAppValidate, Action1 configureApp, Action1 configureTool, Boolean disableHttpEgress, LogLevel profilerLogLevel, String subScenarioName, Boolean startAppBeforeTool) in /_/src/Tests/Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests/Runners/ScenarioRunner.cs:line 77 at Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests.Runners.ScenarioRunner.SingleTarget(ITestOutputHelper outputHelper, IHttpClientFactory httpClientFactory, DiagnosticPortConnectionMode mode, String scenarioName, Func3 appValidate, Func3 postAppValidate, Action1 configureApp, Action1 configureTool, Boolean disableHttpEgress, LogLevel profilerLogLevel, String subScenarioName, Boolean startAppBeforeTool) in /_/src/Tests/Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests/Runners/ScenarioRunner.cs:line 100 at Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests.Runners.ScenarioRunner.SingleTarget(ITestOutputHelper outputHelper, IHttpClientFactory httpClientFactory, DiagnosticPortConnectionMode mode, String scenarioName, Func3 appValidate, Func3 postAppValidate, Action1 configureApp, Action`1 configureTool, Boolean disableHttpEgress, LogLevel profilerLogLevel, String subScenarioName, Boolean startAppBeforeTool) in //src/Tests/Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests/Runners/ScenarioRunner.cs:line 105
at Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests.LiveMetricsTests.TestSystemDiagnosticsMetrics_MeterInstrumentTags() in /_/src/Tests/Microsoft.Diagnostics.Monitoring.Tool.FunctionalTests/LiveMetricsTests.cs:line 380
--- End of stack trace from previous location ---

[github-actions]

Welcome to dotnet-monitor!

Thanks for creating your first issue; let us know what you think of dotnet-monitor by filling out our survey.