Basic OpenTelemetry (OTel) Support

[antonpirker]

Adding basic OpenTelementry (OTel) support to the Sentry SDK. This PR:

• introduces a config option instrumenter where you can choose if peformance data should be collected by Sentry (when set to sentry) or should be collected by OpenTelementry (when set to otel)
• adds a OTel SpanProcessor that can receive spans form OTel and then convert them into Sentry Spans and send them to Sentry.
• adds a OTel Propagator that can receive and propagate trace headers (Baggage) to keep distributed tracing intact.
• adds the possibility to set the start and end time of Sentry Spans (used to be only now())

Fixes #1687

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
sentry-python	✅ Ready (Inspect)	Visit Preview	Nov 17, 2022 at 2:02PM (UTC)

[sl0thentr0py]

@antonpirker I would also recommend splitting this up into separate PRs (especially the API changes) for a clean history and better changelog.

see getsentry/sentry-ruby#1876 (comment)

[antonpirker]

Split up into the following smaller PRs:

• Add constants for sentry-trace and baggage headers #1765
• Add instrumenter config to switch between Otel and Sentry instrumentation. #1766
• Add API to set arbitrary context in Transaction. #1769
• Add API to set custom Span timestamps #1770
• Add function to extract sentry trace info from traceparent string. #1771
• Add Basic OTel integration #1768

Each of these PRs is based on the previous ones, so please review in that order. Merge the previous into master so you only see the relevant changes in the next one.

[antonpirker]

Closing this in favor of the split up PRs mentioned above.