How can I trace IIS lifecycle events in .NET Framework applications using OpenTelemetry?

[hanunna]

Hello,

I have a .NET Framework web application and I am implementing OpenTelemetry instrumentation for it. I have added instrumentation using the packages

OpenTelemetry.Instrumentation.AspNet
OpenTelemetry.Instrumentation.Http
OpenTelemetry.Instrumentation.MySqlData
OpenTelemetry.Instrumentation.StackExchangeRedis

and can see http request, SQL, Redis traces, but I also want to trace IIS lifecycle events like BeginRequest, AuthenticateRequest, ExecuteRequestHandler, etc.

Global.asax.cs has the below code for instrumentation:

_tracerProvider = Sdk.CreateTracerProviderBuilder()
    .AddAspNetInstrumentation()
    .AddHttpClientInstrumentation()
    .AddMySqlDataInstrumentation()
    .AddRedisInstrumentation()
    .AddOtlpExporter()
    .SetResourceBuilder(resourceBuilder)
    .Build();

I do not see these traces by default. From what I understand, I need to implement custom handlers to trace these events. Is there an alternative way to log these traces?

Additionally, since these packages are still in beta, is it advisable to use them in production systems?

I am relatively new to this and need some assistance. Thank you!

[TimothyMothra]

We don't have any instrumentation libraries that log IIS events.
You would need to write that yourself and create your own logs.

With regard to the beta packages, that's going to be use at your own risk.
The code itself is mature and you would get useful telemetry from those libraries, but the stability is dependent on the OpenTelemetry specification.
For example, OpenTelemetry's Database specification is still in development. This means that the attribute names that are recorded may change in a future release.
But if you're willing to take that risk and use those libraries, our community would be grateful for any feedback that you can provide.