Repository navigation
containers: apply EXCLUDE_HTTP_REQUESTS_BY_PATH to inbound HTTP/1 requests - #385
Merged
Merged
Conversation
def
force-pushed
the
inbound-http-path-filter
branch
from
October 21, 2026 18:35
525c14f to
7788fbd
Compare
def
approved these changes
Oct 21, 2026
Member
|
@cooljacob204 thank you! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Disclaimer: I haven't work with go much and have a pretty rudimentary understanding of what's going on in this project. Change is fairly small though and I think straight forward.
The issue in my case is:
EXCLUDE_HTTP_REQUESTS_BY_PATHisn't applied to inboundHTTP/1requests. OutboundHTTP/1, outboundHTTP/2and inboundHTTP/2all checkHttpFilter, but theHTTP/1case inobserveInboundL7doesn't, so excluded paths still end up incontainer_http_inbound_requests_totaland the inbound latency histogram.I ran into this with Matrix, where clients long poll
/_matrix/client/v3/syncfor 30s. Even with/_matrix/client/*/sync*excluded, those requests kept tripping the latency SLO on my reverse proxy.This adds the same check the outbound did in a similar style:
coroot-node-agent/containers/container.go
Lines 856 to 861 in 8b6ef82
I ran the patched agent on my cluster and the
/syncrequests no longer count toward inbound latency, while other requests are still counted.The contributor file says to add tests for changes, but I didn't see any existing tests around these features. Point me in a direction and I'll be happy to add them if needed.