-
Notifications
You must be signed in to change notification settings - Fork 14
Add support for v1 trace payloads in the library interface for DEFAULT scenario #6280
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
Draft
ajgajg1134
wants to merge
6
commits into
main
Choose a base branch
from
andrew.glaude/LibraryV1Support
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+2,199
−821
Conversation
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
Contributor
|
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
To better cover the efficient trace payload (aka V1), this adds support for acting on v1 trace payloads to the default scenario on the tracer side. The agent interface already supported this, but there are far more assertions on the library side of things so this change is very valuable. And in fact this work caught a bug around how appsec
meta_structdata was being handled.Additionally I had to modify utils/build/docker/golang/install_ddtrace.sh to support testing against a specific PR of dd-trace-go for this development. It seems that due to contribs having their own modules the previous
go getcode wouldn't properly handle unreleased/unmerged PRs? But I admit I don't fully understand the motivations here so am willing to adjust these changes as needed!Changes
Access span/trace data through helper methods on the interface to ensure they are payload-format agnostic. I verified this by running with dd-trace-go with v1 enabled.
Much of this change was created with the assistance of Cursor / AI. I (the human) have read and reviewed every line of code though to ensure it is reasonable and accomplishes the desired purpose
Workflow
🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist
tests/ormanifests/is modified ? I have the approval from R&P teambuild-XXX-imagelabel is present