[BUG] UseAzureMonitor does not populate custom properties when using BeginScope about azure-sdk-for-net

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cijothomas @rajkumar-rangaraj @reyang @TimothyMothra @vishweshbankwar.

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cijothomas @rajkumar-rangaraj @reyang @TimothyMothra @vishweshbankwar.

[drilko]

Okay, after doing a bit of research I guess I was a bit confused due to design.
Microsoft.Extensions.Logging.ApplicationInsights includes logger scopes by default, while Azure.Monitor.OpenTelemetry.AspNetCore does not.

My questions is then: Is this intentional?
If yes, I would suggest just some documentation about this behavior as a lot of developers will be migrating and a hint about it would greatly help.

[cijothomas]

Scopes are not enabled by default in OpenTelemetry, so it is expected that one must enable them explicitly to get scopes flowing to any exporter, including AzureMonitor. However, https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore/src/OpenTelemetryBuilderExtensions.cs#L132 is surprising.. Not sure why the distro explicitly have to disable it..

[TimothyMothra]

This is by design. This is an opt-in feature and you're using the correct setting to enable:

builder.Services.Configure<OpenTelemetryLoggerOptions>(options =>
{
    options.IncludeScopes = true;
});

Thanks for your feedback. This behavior is different from Application Insights SDK and we'll update our public documentation.