Skip to content
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

Extending Echo filter to match specific metadata #34110

Closed
wtrocki opened this issue May 13, 2024 · 4 comments
Closed

Extending Echo filter to match specific metadata #34110

wtrocki opened this issue May 13, 2024 · 4 comments
Labels
area/http_filter area/metadata enhancement Feature requests. Not bugs or questions.

Comments

@wtrocki
Copy link

wtrocki commented May 13, 2024

Title: Extending Echo filter to match specific metadata

Description:
Extending Echo filter to support metadataMatcher.

Echo filter is now only Network filter. Refactor would be required to enable echo support in HTTP filters.

Echo filter is quite useful for testing complex envoy configurations. Having ability to enable echo per specific matching criteria would be beneficial.
Creating issue to validate idea - I would like to contribute the change.

Relevant Links
https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/echo/v3/echo.proto

@wtrocki wtrocki added enhancement Feature requests. Not bugs or questions. triage Issue requires triage labels May 13, 2024
@wtrocki wtrocki changed the title Adding Extending Echo filter to match specific metadata May 13, 2024
@ravenblackx ravenblackx added area/metadata area/http_filter and removed triage Issue requires triage labels May 13, 2024
@ravenblackx
Copy link
Contributor

@zuercher maybe?

@zuercher
Copy link
Member

My first thought is that if we were to introduce an HTTP echo filter it should be a separate filter. There's already generic code to implement envoy::type::matcher::v3::MetadataMatcher so I don't think there's going to be a lot of duplication between network and http echo filters that support metadata matching.

I think the first step would be to propose the API changes for the existing echo filter and the new http echo filter and go from there.

cc @htuch @alyssawilk since they nominally own the echo network filter

@htuch
Copy link
Member

htuch commented May 14, 2024

+1, what @zuercher wrote sounds like a plan.

@wtrocki
Copy link
Author

wtrocki commented May 16, 2024

I eventually managed to find much better solution for the problem:
https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/tap_filter

I think tap filter could be mentioned in the documentation as much better alternative to echo filter.

@wtrocki wtrocki closed this as completed May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/http_filter area/metadata enhancement Feature requests. Not bugs or questions.
Projects
None yet
Development

No branches or pull requests

4 participants