Aids in decorating access logs for requests that are subjected to ext_proc and fault calls. In ext_proc, the struct is copied into the filter state object that contains per grpc exchange stats. In fault case, it is copied into dynamicMetadata under the namespace matching the filter config name.
Risk Level: Low
Testing: Unit tests
Signed-off-by: Shriram Rajagopalan <shriramr@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ c2ae2211196a48b12d2e36d00c6c2889ae2f434a
API definition for scrubbing request headers sending from ext_proc filter to ext_proc server
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 7d1b1d0040054093575dcda742099be9641e3a64
Commit Message: [ZK filter] emit fast/slow response metrics for error budget SLI calculation
Additional Description: Emit fast/slow response counter metrics for each opcode used for error budget SLI calculation.
Risk Level: low
Testing: unit tests
Docs Changes: This diff will update these two docs ZooKeeper proxy introduction doc and ZooKeeper proxy proto doc.
Release Notes: [ZK filter] emit fast/slow response metrics for error budget SLI calculation
Platform Specific Features: N/A
API Considerations: Did not find a good way to make repeated message unique (LatencyThreshold in this case) with proto validation. Also found that enum cannot be the key of the proto map.
Signed-off-by: Zhewei Hu <zhu@pinterest.com>
Mirrored from https://github.com/envoyproxy/envoy @ a170b03435c4b12c0b6e46b6b9800f08dba2bdd5
Commit Message: accesslog: support CEL command in the formatter
Risk Level: low
Testing: unit
Docs Changes: none
Release Notes: yes
Mirrored from https://github.com/envoyproxy/envoy @ 8cfeabd5bd0b15b5e6ef029bf9fef4dcaa1c8254
Adding in the ability to disable route cache clearing ont he ext_proc filter. Changing the behavior of the clearing to check if there is a header mutation.
Risk Level: Low
Testing: test/extensions/filters/http/ext_proc/filter_test.cc
Docs Changes: docs/root/configuration/http/http_filters/ext_proc_filter.rst
Release Notes: changelogs/current.yaml
Signed-off-by: Joseph Straceski <jstraceski@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ a3f01a5190b56e576842ac3b08b337c181a02bda
Make deprecation of source_ip documented
Signed-off-by: Raven Black <ravenblack@dropbox.com>
Mirrored from https://github.com/envoyproxy/envoy @ fe274c0277a8633b277f02b720930137280f7529
* [balsa] Add config field to enable custom methods.
This is no behavioral change by default: only methods from a hard-coded
list (that matches the list hard-coded in http-parser, and is slightly
different from the one that will be used by UHV) are accepted.
Then the new knob is true, BalsaParser does the exact same validation as
UHV will by default: method has to be non-empty and only contain allowed
characters.
When UHV method validation logic is turned on in the future, all
validation can be removed from BalsaParser. When non-UHV mode is
deprecated, this new proto field can be removed.
Tracking issue: #21245
Signed-off-by: Bence Béky <bnc@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 8c17c7a8c91380b2ad5d2e352db94fd1c7571d46
Adding a rate limiting for redis client reconnection rate to avoid reconnection storm on redis server
Risk Level: Low
Testing: Unit test, Manual test with redis
Fixes#26400
Signed-off-by: lgao <lgao@roblox.com>
Mirrored from https://github.com/envoyproxy/envoy @ dbec6f88d6d814829f1988d92e888cdc98c34fb1
* [CER] Traverse per route filter hierarchy till match is found.
Mirrored from https://github.com/envoyproxy/envoy @ f63220bdeda9336ce54584e044141eb963d3cb27
Move bazel/utils.bzl into api/bazel
The api/... subtree depends on utils.bzl, but it is stored in //bazel,
not //api/bazel. When the api sub-tree is exported as
"data-plane-api", the resulting repository is not buildable.
This attempts to fix that by changing the canonical location of
utils.bzl and updating the references to it.
Signed-off-by: Ryan Anderson <ryan@michonline.com>
Mirrored from https://github.com/envoyproxy/envoy @ 35ef2c4eeac8e930e3c00e40baaea5271590db41
The gRPC xDS implementation uses hardcoded retry durations for re-establishing the gRPC channel. This change makes the backoff parameters configurable.
Risk Level: Low
Testing: unit test
Fixes#24236
Signed-off-by: Jayson Dmello <jdmello@confluent.io>
Mirrored from https://github.com/envoyproxy/envoy @ 672b41532a9f03bc84fbbfec0d1db5b633833f9c
Commit Message:
Additional Description: Follow up to #26155, enabling a similar feature for upstream access logs - record an access log on upstream connection established, if requested.
Risk Level: Low
Testing: Unit tests, integration tests
Docs Changes: router API
Release Notes: none
Platform Specific Features: none
Signed-off-by: Ohad Vano <ohadvano@gmail.com>
Signed-off-by: ohadvano <49730675+ohadvano@users.noreply.github.com>
Mirrored from https://github.com/envoyproxy/envoy @ 49a2fc0e4dbfd608737d06ab0a9b94ca4fc73104
Commit Message: Adds a protocol option for which HTTP/2 codec to use.
Additional Description:
Risk Level: low
Testing: ran unit tests and integration tests locally
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features:
Signed-off-by: Biren Roy <birenroy@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 73115db835f27a79a79a44b8ee8f7ac4333891c7
Commit Message: Allow only histogram summaries in metric service
Additional Description: Histogram metrics by default send two metrics Summary (containing quantiles) and Histogram (containing all the buckets), this makes payloads extremely large when handling lots of stats. In some cases, only having the summary is enough, since we can get sum, count, and percentiles. Furthermore, it probably only makes sense to send one of both, if I were to need buckets, then Summary is probably useless.
Risk Level: low, off by default
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
Signed-off-by: Sebastian Schepens <sebastian.schepens@mercadolibre.com>
Mirrored from https://github.com/envoyproxy/envoy @ c40aca4c1b51f2089fd33e70b393041c6b291064
data-plane-api(Azure Pipelines)