-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add request id to HTTP transactions to allow tracking. #28590
Conversation
This pull request does not have a backport label. Could you fix it @scunningham? 🙏
NOTE: |
💚 Build Succeeded
Expand to view the summary
Build stats
❕ Flaky test reportNo test was executed to be analysed. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
/test |
2 similar comments
/test |
/test |
…xy into Fleet Server and back.
e3fc982
to
48b8b49
Compare
/test |
* Add request id to HTTP transactions to allow tracking through the proxy into Fleet Server and back. * Linter fix (cherry picked from commit 6288ccc)
* Add request id to HTTP transactions to allow tracking through the proxy into Fleet Server and back. * Linter fix (cherry picked from commit 6288ccc) Co-authored-by: Sean Cunningham <[email protected]>
What does this PR do?
Adds the "X-Request-ID" header to HTTP transactions with Fleet Server.
Why is it important?
This allows tracking of the transaction through the cloud proxy and into Fleet Server. The request Id can be aligned across log entries.
Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.