feat: support trace to profile correlation for native using custom labels#136
Draft
elsakeirouz wants to merge 9 commits intomainfrom
Draft
feat: support trace to profile correlation for native using custom labels#136elsakeirouz wants to merge 9 commits intomainfrom
elsakeirouz wants to merge 9 commits intomainfrom
Conversation
elsakeirouz
added
enhancement
…bels * go.mod, * go.sum, * main.go, * reporter/datadog_reporter.go: Here.
elsakeirouz
force-pushed
the
elsa/custom-labels-for-native
branch
from
033eef4 to
7bb07c6
Compare
nsavoire
force-pushed
the
nsavoire/update_upstream
branch
3 times, most recently
from
f54d1b2 to
76967b1
Compare
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
2 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.
TODO: update this
What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request? In order to motivate your point, it may be valuable to explain why this change is useful or what problem is being solved.
Additional Notes
This is the section to put technical guidance/constraints, call out potential regressions, cite sources, and in general offer some exposition on the how of the PR. This section doesn't need to be incredibly detailed, but it makes life easier for reviewers!
How to test the change?
Describe here in detail how the change can be validated. This is a great section to call out specific tests you've added or improved, or to acknowledge code sections which are particularly difficult to test.