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

Make transaction names work #3643

Merged
merged 1 commit into from
Oct 11, 2024
Merged

Make transaction names work #3643

merged 1 commit into from
Oct 11, 2024

Conversation

sl0thentr0py
Copy link
Member

  • while sending the event in the final payload, the transaction name will be picked up from the attributes sentry.name or fallback to the description when we only have otel instrumentation
  • for populating DSC in the head case, we are doing a best attempt solution and fetching the transaction name/source from the current and isolation scopes
    • NOTE that there are cases where this will be inaccurate if we never set the transaction name on the scope in some integration, so we will go through and fix those cases separately.

Copy link

codecov bot commented Oct 10, 2024

❌ 2940 Tests Failed:

Tests completed Failed Passed Skipped
20072 2940 17132 4443
View the top 3 failed tests by shortest run time
tests.integrations.litestar.test_litestar test_middleware_callback_spans
Stack Traces | 0s run time
No failure message available
tests.integrations.litestar.test_litestar test_middleware_callback_spans
Stack Traces | 0s run time
No failure message available
tests.integrations.litestar.test_litestar test_middleware_partial_receive_send
Stack Traces | 0s run time
No failure message available

To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard

Copy link
Contributor

@sentrivana sentrivana left a comment

Choose a reason for hiding this comment

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

Makes sense to me. Just two small comments about the api.

* while sending the event in the final payload, the transaction name
  will be picked up from the attributes `sentry.name` or fallback to the
  `description` when we only have otel instrumentation
* for populating DSC in the head case, we are doing a best attempt
  solution and fetching the transaction name/source from the current and
  isolation scopes
    * NOTE that there are cases where this will be
      inaccurate if we never set the transaction name on the scope in some
      integration, so we will go through and fix those cases separately.
@sl0thentr0py sl0thentr0py merged commit e205f2d into potel-base Oct 11, 2024
3 of 13 checks passed
@sl0thentr0py sl0thentr0py deleted the neel/potel/tx-name branch October 11, 2024 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants