Auto-instrumentation layer for .NET

[harveyrendell]

We have a number of dotnet lambda functions which we would like to instrument via OpenTelemetry.

Auto-instrumentation for dotnet is now available, but there is no dotnet layer that supports auto-instrumentation. Is this functionality planned to be added at some point in the future?

This was raised previously here: #571

Thanks

[tylerbenson]

We don't have anyone with .NET experience participating in the SIG right now. If you'd like to contribute, we'd love your participation.

[harveyrendell]

I'll take a look at what's involved and see if I can get this added 👍

[tylerbenson]

See also: #532

[harveyrendell]

Looking for some guidance on an approach here. At the moment there isn't support for AWS SDK tracing inside opentelemetry-dotnet-instrumentation but the automatic instrumentation does work out of the box with lambda as a layer, but without a lot of useful telemetry.

Some pre-requisites I see are:

• AWS API tracing support inside the dotnet autoinstrumentation Bringing AWS Api call tracing to auto instrumentation opentelemetry-dotnet-instrumentation#3391 Aws sdk api phase1 opentelemetry-dotnet-instrumentation#3401
• Checking that the lambda lifecycle management with auto-instrumentation enabled. The manual instrumentation library has wrapper functions for this already but may need to be adjusted to work here. https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.AWSLambda

[tylerbenson]

Have you talked to the folks in the .NET SIG? If they're onboard, we can try to go over the Java instrumentation in the Lambda SIG and pick out some technical requirements for what you might need in .NET.