Deprecate Sentry.Azure.Functions.Worker

[jamescrosswell]

Description

Currently we have an Sentry.Azure.Functions.Worker integration which adds some middleware that just starts/stops a transaction for every request.

This could be done instead using our OpenTelemetry integration. Potentially then, we could remove the Sentry.Azure.Functions.Worker NuGet package and replace this with a sample app that showed how to wire everything up with Microsoft.Extensions.Logging and OpenTelemetry.

See:

• Microsoft.Azure.Functions.Worker.Sdk crashes azure function with http trigger #4468 (comment)

This is the current output from our Azure.Functions.Worker sample:

This is what you see when using OpenTelemetry:

[linear]

NET-445 Consider deprecating Sentry.Azure.Functions.Worker

[jamescrosswell]

The OpenTelemetry instrumentation is broadly equivalent... it uses the name of the function instead of the name of the HTTP route for the Span.Name (which is arguably better). We could probably even tweak that if we really wanted to, via an OTEL enricher... but not necessary IMO.

I think we remove our Sentry.Azure.Functions.Worker package. It adds little value and is just another thing to maintain.