-
Notifications
You must be signed in to change notification settings - Fork 148
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
Handle requests for /processes/apm-server. #1792
Merged
cmacknz
merged 2 commits into
elastic:main
from
cmacknz:translate-apm-server-process-id
Nov 24, 2022
Merged
Handle requests for /processes/apm-server. #1792
cmacknz
merged 2 commits into
elastic:main
from
cmacknz:translate-apm-server-process-id
Nov 24, 2022
Conversation
This file contains 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
Add special handling for the apm-server process ID for the /processes/$ID route as well as the /processes response body. V2 changed the process IDs used for these APIs, which has broken health checks in the cloud provisioning infrastructure. It is much faster to add a few lines of code to special case this in the agent than it is to update all of the cloud monitoring infrastructure.
cmacknz
added
Team:Elastic-Agent
Label for the Agent team
v8.6.0
skip-changelog
backport-v8.6.0
Automated backport with mergify
labels
Nov 24, 2022
cmacknz
requested review from
michalpristas and
blakerouse
and removed request for
a team
November 24, 2022 20:02
🌐 Coverage report
|
Tested locally with an agent running the APM integration. Going to merge this to try to fix the snapshot, otherwise will likely be waiting several days for a review. |
mergify bot
pushed a commit
that referenced
this pull request
Nov 24, 2022
Handle requests for /processes/apm-server. Add special handling for the apm-server process ID for the /processes/$ID route as well as the /processes response body. V2 changed the process IDs used for these APIs, which has broken health checks in the cloud provisioning infrastructure. It is much faster to add a few lines of code to special case this in the agent than it is to update all of the cloud monitoring infrastructure. (cherry picked from commit 378a412)
cmacknz
added a commit
that referenced
this pull request
Nov 24, 2022
Handle requests for /processes/apm-server. Add special handling for the apm-server process ID for the /processes/$ID route as well as the /processes response body. V2 changed the process IDs used for these APIs, which has broken health checks in the cloud provisioning infrastructure. It is much faster to add a few lines of code to special case this in the agent than it is to update all of the cloud monitoring infrastructure. (cherry picked from commit 378a412) Co-authored-by: Craig MacKenzie <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport-v8.6.0
Automated backport with mergify
skip-changelog
Team:Elastic-Agent
Label for the Agent team
v8.6.0
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.
Add special handling for the apm-server process ID for the /processes/$ID route as well as the /processes response body.
V2 changed the process IDs used for these APIs, which has broken health checks in the cloud provisioning infrastructure. It is much faster to add a few lines of code to special case this in the agent than it is to update all of the cloud monitoring infrastructure.