Skip to content

Count HTTP/2 clients in IP connection metrics - #13582

Open
bneradt wants to merge 1 commit into
apache:masterfrom
bneradt:fix-client-connection-ip-metrics
Open

Count HTTP/2 clients in IP connection metrics#13582
bneradt wants to merge 1 commit into
apache:masterfrom
bneradt:fix-client-connection-ip-metrics

Conversation

@bneradt

@bneradt bneradt commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

The IPv4 and IPv6 client connection metrics only count HTTP/1 sessions,
so deployments using HTTP/2 report fewer accepted connections than
Traffic Server actually handles.

This patch moves address-family accounting into the shared proxy session
and applies it to every supported HTTP protocol. It also adds replay
coverage and updates the existing mixed-protocol metric expectation.

Fixes: #12105

The IPv4 and IPv6 client connection metrics only count HTTP/1 sessions,
so deployments using HTTP/2 report fewer accepted connections than
Traffic Server actually handles.

This patch moves address-family accounting into the shared proxy session
and applies it to every supported HTTP protocol. It also adds replay
coverage and updates the existing mixed-protocol metric expectation.

Fixes: apache#12105
Copilot AI lite review requested due to automatic review settings August 21, 2026 20:43
@bneradt bneradt added this to the 11.0.0 milestone Aug 21, 2026
@bneradt bneradt self-assigned this Aug 21, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

total_client_connections_ipv4/6 is only incremented if HTTP/1.x is used

2 participants