Skip to content

[8.19] (backport #4979) [APM] Add known issue for HTTP/2 strict client framing failures#4980

Merged
carsonip merged 2 commits into8.19from
mergify/bp/8.19/pr-4979
Apr 21, 2026
Merged

[8.19] (backport #4979) [APM] Add known issue for HTTP/2 strict client framing failures#4980
carsonip merged 2 commits into8.19from
mergify/bp/8.19/pr-4979

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Apr 21, 2026

Summary

  • Add an APM known-issue entry for HTTP/2 framing/protocol failures seen with strict clients.
  • Document affected 8.x versions, user-visible symptoms, workaround guidance, and the 8.19.15 fix version.
  • Exclude 9.x version mentions to keep this scoped to the 8.x docs stream.

Corresponds to 9.x doc change elastic/apm-server#20911

Part of elastic/apm-server#20887

Made with Cursor


This is an automatic backport of pull request #4979 done by Mergify.

* docs: add APM HTTP/2 strict client known issue for 8.x

Document the HTTP/2 framing/protocol failure symptoms, workaround guidance, and 8.19.15 fix version in APM known issues without 9.x references.

* docs: align HTTP/2 known-issue wording with apm-server

Match the source known-issue details and wording for strict HTTP/2 client framing failures, while keeping the entry scoped to 8.x versions.

Made-with: Cursor

* docs: use source wording for HTTP/2 workaround

Made-with: Cursor

* docs: explicitly label HTTP/2 guidance as workaround

Made-with: Cursor

* docs: align workaround section with known-issues prose style

Made-with: Cursor

* Apply suggestions from code review

Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>

---------

Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>
(cherry picked from commit 81a1950)

# Conflicts:
#	docs/en/observability/apm/known-issues.asciidoc
@mergify mergify Bot requested a review from a team as a code owner April 21, 2026 15:10
@mergify mergify Bot added backport conflicts There is a conflict in the backported pull request labels Apr 21, 2026
@mergify
Copy link
Copy Markdown
Contributor Author

mergify Bot commented Apr 21, 2026

Cherry-pick of 81a1950 has failed:

On branch mergify/bp/8.19/pr-4979
Your branch is up to date with 'origin/8.19'.

You are currently cherry-picking commit 81a19502.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/en/observability/apm/known-issues.asciidoc

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@github-actions
Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@carsonip carsonip enabled auto-merge (squash) April 21, 2026 15:53
@carsonip carsonip merged commit d8916db into 8.19 Apr 21, 2026
6 checks passed
@carsonip carsonip deleted the mergify/bp/8.19/pr-4979 branch April 21, 2026 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport conflicts There is a conflict in the backported pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant