Open safakgur opened 10 months ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @AzmonActionG @AzmonAlerts @AzMonEssential @AzmonLogA @dadunl @SameergMS.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @AzmonActionG @AzmonAlerts @AzMonEssential @AzmonLogA @dadunl @SameergMS.
Library name and version
Azure.Monitor.OpenTelemetry.AspNetCore 1.0.0
Query/Question
I use Azure.Monitor.OpenTelemetry.AspNetCore 1.0.0 to add OTel
HttpClient
instrumentation and Azure Monitor exporter.On
1.0.0-beta.7
, I was able to do the following:But with the new version,
AspNetCoreInstrumentationOptions
is made internal.So, what's the new, recommended way of enriching the request activity?
One alternative I've been experimenting with is moving away from this do-it-all package to the following, more granular packages:
OpenTelemetry.Instrumentation.AspNetCore
(comes with a publicAspNetCoreTraceInstrumentationOptions
class)Azure.Monitor.OpenTelemetry.Exporter
OpenTelemetry.Extensions.Hosting
...but I'd rather keep this one if it provides the same features.
Environment
Windows 10 .NET 8.0.100 Visual Studio 17.8.0