[APM] Add v2 of the evp_proxy endpoint #13825
Merged
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
|
LGTM 🙌 |
dianashevchenko
approved these changes
Oct 11, 2022
albertvaka
added a commit
that referenced
this pull request
Oct 11, 2022
albertvaka
added a commit
that referenced
this pull request
Oct 11, 2022
This was referenced Oct 24, 2022
guyarb
pushed a commit
that referenced
this pull request
Oct 25, 2022
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.
What does this PR do?
In #13212 we added a new feature to the EVP Proxy. However, there was no way for tracers to know if the new feature is available or not in the Agent, since we didn't bump the version.
Although this feature is also supported in the
v1API (since it's not a breaking change forv1), we want to add a way to tell our tracers that this version of the Agent supports the new feature by adding av2API.