Support Python SDK 3.0.0

[antonpirker]

Update the codebase so it works with Sentry Python SDK 3.0.0 alpha.

Sentry SDK 3.0.0 has some backwards incompatibilities and uses Opentelementry under the hood to create spans.

What this PR does:

• replace sentry_sdk.start_transaction() with sentry_sdk.start_span()
• replace span.set_data() with span.set_attribute()
• replace scope.transaction with scope.root_span
• replace Span.containing_transaction with Span.root_span
• replace custom_sampling_context with attributes parameter
• replace sentry_sdk.scope.get_*_scope() with sentry_sdk.get_*_scope()
• replace one scope.add_attachment() with sentry_sdk.add_attachment()
• change one continue_trace() to the new context manager.
• update traces_sampler to use new sampling_context format
• added a few tests

See also the migration guide:
https://docs.sentry.io/platforms/python/migration/2.x-to-3.x

---

Related, but split out into separate PRs:

• make sure traces_sampler works the same as before (check for sample_rate): test: Add test for custom sample rates #93011
• make all get_isolation_scope calls use the top-level API. Currently, some calls where we from sentry_sdk import Scope then call Scope.get_isolation_scope still need to be converted to the top-level API: Cleanup imports to always use the top level api. #93307
• check event["measurements"] places if those can be removed (because SDK does not support measurements anymore): Remove usage of measurements in favor of span.data. #92718
• change set_span_data() to set_span_attribute() but check for value NOT be a dict: ref: Rename set_span_data to set_span_attribute #92946
• replace with sentry_sdk.init(dsn=...) with with sentry_sdk.new_scope() as scope: scope.set_client(sentry_sdk.Client(dsn=...)) in src/sentry/runner/main.py: ref: Use set_client to change DSN #92944
• remove propagate_hub=True from ThreadingIntegration: ref: Remove propagate_hub to ThreadingIntegration #93016
• remove minimetrics from the sentry codebase, because the metrics product was never released: Remove minimetrics #93595
• https://github.com/getsentry/getsentry/pull/17553
• chore: Make devenv forward compatible with Sentry SDK 3.0.0 devenv#194
• chore: Make devservices forward compatible with Python SDK 3.0.0 devservices#277
• Make compatible with sentry sdk 3.0.0 pytest-sentry#39
• Update Python migration guide sentry-docs#13939

[codecov]

Codecov Report

Attention: Patch coverage is 92.55319% with 14 lines in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/sentry/stacktraces/processing.py	0.00%	5 Missing ⚠️
src/sentry/replays/usecases/ingest/__init__.py	0.00%	2 Missing ⚠️
src/sentry/tempest/tasks.py	0.00%	2 Missing ⚠️
src/sentry/api/base.py	0.00%	1 Missing ⚠️
src/sentry/cache/base.py	0.00%	1 Missing ⚠️
src/sentry/processing/backpressure/monitor.py	0.00%	1 Missing ⚠️
src/sentry/scim/endpoints/utils.py	66.66%	1 Missing ⚠️
src/sentry/utils/snuba.py	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #92011      +/-   ##
==========================================
+ Coverage   84.22%   88.00%   +3.78%     
==========================================
  Files       10441    10439       -2     
  Lines      603621   603584      -37     
  Branches    23491    23444      -47     
==========================================
+ Hits       508384   531177   +22793     
+ Misses      94871    71901   -22970     
- Partials      366      506     +140     

[asottile-sentry]

did you end up fixing the leaky sdk bits in pytest-sentry that were causing the code under test to report to the tests project?

[antonpirker]

was sidetracked by ai agents stuff, so this is still on my list.

[antonpirker]

@asottile-sentry do you know if those errors I get ( django.db.utils.OperationalError: ObjectInUse('database "test_region" is being accessed by other users\nDETAIL: There are 12 other sessions using the database.\n') are flakes?

[asottile-sentry]

@asottile-sentry do you know if those errors I get ( django.db.utils.OperationalError: ObjectInUse('database "test_region" is being accessed by other users\nDETAIL: There are 12 other sessions using the database.\n') are flakes?

this means some background thread started a database connection in some test (it's pretty hard to actually narrow down). it's likely caused by this PR unfortunately :(

[untitaker]

this means some background thread started a database connection in some test (it's pretty hard to actually narrow down). it's likely caused by this PR unfortunately :(

I think this flake also exists on main. @joshuarli tagged me in a flaky test ticket that had the same issue.

[asottile-sentry]

this means some background thread started a database connection in some test (it's pretty hard to actually narrow down). it's likely caused by this PR unfortunately :(

I think this flake also exists on main. @joshuarli tagged me in a flaky test ticket that had the same issue.

it's a bit flaky on mainline yeah -- but not to the level it is failing here

[sl0thentr0py]

only one test is failing now after the pytest-sentry update, I think that substantially reduced the reports here
https://sentry.sentry.io/issues/?project=2423079&query=is%3Aunresolved%20pytest_environ.GITHUB_REF%3Arefs%2Fpull%2F92011%2Fmerge&referrer=issue-list&statsPeriod=1h
but there's still a few of them that I think are valid? please correct me if I'm wrong!

[untitaker]

the test failure you see here is present on master, it's currently being debugged

[getsentry-bot]

revert failed (conflict? already reverted?) -- check the logs

[sentrivana]

Reverted because a change in issue grouping introduced by this release backlogged canary. We'll fix this and dogfood again next week.