Implicit OpenTelemetry initialization

[jamescrosswell]

Related to:

• .NET SDK powered by OTel #3159

Overview

If we're going to build upon OpenTelemetry and leverage this behind the scenes for Tracing, we don't want to add complexity for people who are currently using Sentry for Tracing. One important aspect of that is initialization.

At the moment if you want to use Sentry with OpenTelemetry for Tracing, initialization is a two step process.

1. You need to Initialize OpenTelemetry... e.g.:
   

   sentry-dotnet/samples/Sentry.Samples.OpenTelemetry.Console/Program.cs

   Lines 23 to 30 in bd62cf0

   	using var tracerProvider = Sdk.CreateTracerProviderBuilder()
   	.AddSource(serviceName)
   	.ConfigureResource(resource =>
   	resource.AddService(
   	serviceName: serviceName,
   	serviceVersion: serviceVersion))
   	.AddSentry() // <-- Configure OpenTelemetry to send traces to Sentry
   	.Build();

2. You need to configure Sentry:
   

   sentry-dotnet/samples/Sentry.Samples.OpenTelemetry.Console/Program.cs

   Lines 16 to 21 in bd62cf0

   	SentrySdk.Init(options =>
   	{
   	// options.Dsn = "... Your DSN ...";
   	options.TracesSampleRate = 1.0;
   	options.UseOpenTelemetry(); // <-- Configure Sentry to use OpenTelemetry trace information
   	});

And the stuff you configure in step 1 has to match the stuff you configure in Step 2... You can't call UseOpenTelemetry when initializing Sentry if you haven't called UseSentry when initializing OpenTelemetry.

Ideally, particularly if users don't even know (or care) that OpenTelemetry is being used behind the scenes, this would be a seamless one step process.

[jamescrosswell]

We didn't find any straight forward way to do this.