Skip to content

Remove span streaming branches from integrations #6997

Closed
51 of 51 issues completed
Closed

Description

@sentrivana

Open a branch off of major/3.0. The resulting PR should also be against major/3.0.

Remove transaction-based tracing from integrations:

  • Whenever we branch based on has_span_streaming_enabled, only keep the span streaming branch and remove the legacy branch.
  • Clean up any compatibility utils like local set_on_span functions, special span_mgr/span_ctx variables if not needed anymore, etc.
  • In tests, remove any non-span-streaming test cases/branches and rename the remaining tests (the _span_streaming suffix, if they have one, is not necessary anymore).

Activity

  1. linear-code commented on Aug 3, 2026

    @linear-code
  2. alexander-alderman-webb commented on Aug 3, 2026

    @alexander-alderman-webb
    Collaborator

    We'll do this in one go or integration by integration?

  3. sentrivana commented on Aug 3, 2026

    @sentrivana
    CollaboratorAuthor

    It's not reviewable in one go. Either integration by integration or by bunching up a handful of similar integrations.

  4. 33 remaining items

  5. self-assigned this
    on Aug 11, 2026
  6. pnagre05 commented on Aug 12, 2026

    @pnagre05

    I can look into working on the redis integration if nobody has started working on it - otherwise asyncio or aiohttp are issues I can pick up as well.

  7. moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on Aug 12, 2026
  8. moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3on Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions