diff --git a/envoy/extensions/filters/http/router/v3/router.proto b/envoy/extensions/filters/http/router/v3/router.proto index 6ab64f92..ce595c05 100644 --- a/envoy/extensions/filters/http/router/v3/router.proto +++ b/envoy/extensions/filters/http/router/v3/router.proto @@ -19,7 +19,7 @@ option (udpa.annotations.file_status).package_version_status = ACTIVE; // Router :ref:`configuration overview `. // [#extension: envoy.filters.http.router] -// [#next-free-field: 7] +// [#next-free-field: 8] message Router { option (udpa.annotations.versioning).previous_message_type = "envoy.config.filter.http.router.v2.Router"; @@ -78,4 +78,14 @@ message Router { // :ref:`config_http_filters_router_x-envoy-expected-rq-timeout-ms` header, populated by egress // Envoy, when deriving timeout for upstream cluster. bool respect_expected_rq_timeout = 6; + + // If set, Envoy will avoid incrementing HTTP failure code stats + // on gRPC requests. This includes the individual status code value + // (e.g. upstream_rq_504) and group stats (e.g. upstream_rq_5xx). + // This field is useful if interested in relying only on the gRPC + // stats filter to define success and failure metrics for gRPC requests + // as not all failed gRPC requests charge HTTP status code metrics. See + // :ref:`gRPC stats filter` documentation + // for more details. + bool suppress_grpc_request_failure_code_stats = 7; } diff --git a/envoy/extensions/filters/http/router/v4alpha/router.proto b/envoy/extensions/filters/http/router/v4alpha/router.proto index d0baaab8..2d72bd14 100644 --- a/envoy/extensions/filters/http/router/v4alpha/router.proto +++ b/envoy/extensions/filters/http/router/v4alpha/router.proto @@ -19,7 +19,7 @@ option (udpa.annotations.file_status).package_version_status = NEXT_MAJOR_VERSIO // Router :ref:`configuration overview `. // [#extension: envoy.filters.http.router] -// [#next-free-field: 7] +// [#next-free-field: 8] message Router { option (udpa.annotations.versioning).previous_message_type = "envoy.extensions.filters.http.router.v3.Router"; @@ -78,4 +78,14 @@ message Router { // :ref:`config_http_filters_router_x-envoy-expected-rq-timeout-ms` header, populated by egress // Envoy, when deriving timeout for upstream cluster. bool respect_expected_rq_timeout = 6; + + // If set, Envoy will avoid incrementing HTTP failure code stats + // on gRPC requests. This includes the individual status code value + // (e.g. upstream_rq_504) and group stats (e.g. upstream_rq_5xx). + // This field is useful if interested in relying only on the gRPC + // stats filter to define success and failure metrics for gRPC requests + // as not all failed gRPC requests charge HTTP status code metrics. See + // :ref:`gRPC stats filter` documentation + // for more details. + bool suppress_grpc_request_failure_code_stats = 7; }