-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[journeys] use http2 by default #247883
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
Merged
Merged
[journeys] use http2 by default #247883
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
nickofthyme
approved these changes
Jan 6, 2026
jbudz
approved these changes
Jan 6, 2026
Contributor
Author
|
/ci |
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
|
merge conflict between base and head |
Contributor
Author
|
@dmlemeshko could you take a look at this one? |
dmlemeshko
approved these changes
Jan 15, 2026
Contributor
💚 Build Succeeded
Metrics [docs]Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
|
dennis-tismenko
pushed a commit
to dennis-tismenko/kibana
that referenced
this pull request
Jan 22, 2026
## Summary Switches all journeys to use HTTP2 by default (unless a custom FTR config is defined). Also, removes the http2-specific dashboard journeys since they won't be distinct anymore. Journey run: https://buildkite.com/elastic/kibana-single-user-performance/builds/18426 --------- Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Dzmitry Lemechko <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport:skip
This PR does not require backporting
release_note:skip
Skip the PR/issue when compiling release notes
v9.4.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.
Summary
Switches all journeys to use HTTP2 by default (unless a custom FTR config is defined).
Also, removes the http2-specific dashboard journeys since they won't be distinct anymore.
Journey run: https://buildkite.com/elastic/kibana-single-user-performance/builds/18426