Skip to content

Conversation

@mosche
Copy link
Contributor

@mosche mosche commented Jul 2, 2025

Prevent trace context propagation for self-rescheduling operations to not create everlasting APM transactions.

Relates to ES-10969

@mosche mosche requested a review from a team July 2, 2025 14:46
@mosche mosche added >non-issue :Core/Infra/Core Core issues without another label labels Jul 2, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Core/Infra Meta label for core/infra team label Jul 2, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@elasticsearchmachine elasticsearchmachine added v9.2.0 serverless-linked Added by automation, don't add manually labels Jul 2, 2025
Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer that we make sure these tasks don't run in a tracing context right from the start (i.e. the point at which they're launched and conceptually detach themselves from the calling operation). The lack of tracing should then propagate automatically to the future-scheduled operations, as well as all the other operations that they run.

I'm ok with adding some assertions in these places to verify that we didn't accidentally start tracing anything, but it would be a bug to need to actually change the context each iteration as done here.

@mosche
Copy link
Contributor Author

mosche commented Jul 4, 2025

As discussed, closing this in favor of #130607

@mosche mosche closed this Jul 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Core/Infra/Core Core issues without another label >non-issue serverless-linked Added by automation, don't add manually Team:Core/Infra Meta label for core/infra team v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants