feat(tracing): Allow to set instrumenter on Span & Transaction#6136
Merged
feat(tracing): Allow to set instrumenter on Span & Transaction#6136
instrumenter on Span & Transaction#6136Conversation
This defaults to `sentry` if not set.
4 tasks
Contributor
size-limit report 📦
|
AbhiPrasad
approved these changes
Nov 8, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A span & transaction now have a field
instrumenterthat can be used to check where a the span/transaction was created.This defaults to
sentry.In later steps, we can use this information to react internally based on SDK config.
ref #6127