Skip to content

Commit 31fb194

Browse files
committed
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.
1 parent 13d7339 commit 31fb194

1 file changed

Lines changed: 14 additions & 0 deletions

File tree

docs/en/observability/apm/known-issues.asciidoc

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,20 @@ _Versions: XX.XX.XX, YY.YY.YY, ZZ.ZZ.ZZ_
2121
// If applicable, link to fix
2222
////
2323

24+
[discrete]
25+
== HTTP/2 connections may fail with strict clients due to framing issues
26+
27+
_Elastic Stack versions: 8.19.12, 8.19.13, 8.19.14_ +
28+
_Fixed in Elastic Stack version 8.19.15_
29+
30+
The issue occurs when using APM Server over HTTP/2 with strict clients.
31+
Affected clients may report errors such as `Error in the HTTP2 framing layer`,
32+
`Failure when receiving data from the peer`, or browser `net::ERR_HTTP2_PROTOCOL_ERROR`.
33+
34+
As a workaround, use HTTP/1.1 between clients and APM Server, or offload HTTP/2 through a non-strict load balancer or proxy.
35+
36+
This issue is fixed in 8.19.15 (https://github.com/elastic/apm-server/pull/20908[elastic/apm-server#20908]).
37+
2438
[discrete]
2539
== Tail Sampling may not compact / expired TTLs as quickly as desired, causing increased storage usage.
2640

0 commit comments

Comments
 (0)