Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start a new trace (or root activity) for delayed messages #7049

Merged
merged 22 commits into from
Jun 3, 2024

Conversation

lailabougria
Copy link
Contributor

@lailabougria lailabougria commented May 31, 2024

Addresses:

This change ensures that anytime a message is delayed, we ensure to start a new root activity and never create a child span.

Delayed messages can occur when:

  • A timeout is requested in a saga
  • A message is delayed by the user, through the SendOptions API
  • A message is delayed by delayed retries

This is important for tail-sampling scenarios in which a sampling decision is at a point in time, so we want to avoid any delayed operations to be in there.

Documentation: https://docs.particular.net/nservicebus/operations/opentelemetry#traces-delayed-messages

…nceTestingTransport to enable native delayed delivery in the tests that require it
@lailabougria
Copy link
Contributor Author

@ramonsmits addressed your comments

@lailabougria lailabougria merged commit 5a66d8e into master Jun 3, 2024
3 checks passed
@lailabougria lailabougria deleted the new-trace-for-delayed-msgs branch June 3, 2024 15:31
@lailabougria lailabougria added this to the 9.1.0 milestone Jun 25, 2024
@SzymonPobiega SzymonPobiega changed the title Start a new trace (or root activity) for delayed msgs Start a new trace (or root activity) for delayed messages Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants