Expose max_buffered_{rx/tx}_bytes in the Tap filter

[sadieleob]

Gloo Edge Product

Enterprise

Gloo Edge Version

1.17

Is your feature request related to a problem? Please describe.

This is not related to an issue.

Describe the solution you'd like

The customer is asking to expose:

• max_buffered_rx_bytes
• max_buffered_tx_bytes
• record_headers_received_time
• record_downstream_connection

The customer stated that without the max_buffered_<rx/tx>_bytes fields set, the maximum body size is 1KiB that can be sent to the tap filter. Unfortunately, this max body size blocks our integration of the tap filter with their "in-house monetization" project since it requires payloads up to 4KB.

https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/tap/v3/common.proto#config-tap-v3-outputconfig
https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/tap/v3/tap.proto#extensions-filters-http-tap-v3-tap

Describe alternatives you've considered

There are no alternatives

Additional Context

No response

Related Issues

• https://github.com/solo-io/solo-projects/issues/5455
• Implement Streaming support in TAP filter #9845

┆Issue is synchronized with this Asana task by Unito

[soloio-bot]

Zendesk ticket #3974 has been linked to this issue.

[nfuden]

https://github.com/solo-io/solo-projects/issues/5455 encompasses this as well. @DuncanDoyle

[DuncanDoyle]

@nfuden As discussed, removing the "Streaming support" from this requirement an putting this in a separate issue: #9845