Send operation name for function#3311
Merged
Merged
Conversation
trask
approved these changes
Sep 28, 2023
jeanbisutti
approved these changes
Oct 2, 2023
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Contributor
Author
|
@trask Kaibo had done testing and i was able to confirm operation_name showed up in traces and dependencies. |
Member
|
thx @kaibocai! |
trask
reviewed
Oct 11, 2023
trask
approved these changes
Oct 12, 2023
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.
Fix #3066
OperationName will set it directly to operation_name column.
no need to update it in LogDataMapper::setFunctionExtraTraceAttributes, i.e. it's not available in customDimensions column.