forked from emissary-ingress/emissary
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix grpc_stats default behavior with envoy upgrade
The existing behavior in Envoy 1.17 was to produce grpc_stats with the following naming schemes `envoy_cluster_grpc_{ServiceName}_*` when setting `all_methods` or `services` within the grpc_stats config on a `Module`. When neither were set it would aggregate it to `envoy_cluster_grpc_*`. The new behavior since Envoy 1.18 will produce metrics with the following naming scheme `envoy_cluster_grpc_{MethodName}_*` and `envoy_cluster_grpc_*`. Based on great investigation from Luke Shumaker, both versions seems to be improperly parsing the ServiceName. Especially, when a more complex ServiceName such as `cncf.telepresence.Manager/Status` is used. This parsing logic will need to be fixed in upstream Envoy. This commit also adds unit test for how the `grpc_stats` are parsed from the Module and used to configure the filter. If a user provided an empty set: ```yaml apiVersion: getambassador.io/v3alpha1 kind: Module metadata: name: ambassador spec: config: grpc_stats: {} ``` Then this would be equivalent to setting `grpc_stats.all_methods=false`. When setting it with missing fields like such: ```yaml apiVersion: getambassador.io/v3alpha1 kind: Module metadata: name: ambassador spec: config: grpc_stats: ``` This will be equivalent to not being set at all and `grpc_stats` will be disabled. Co-authored-by: Luke Shumaker <[email protected]> Signed-off-by: Lance Austin <[email protected]>
- Loading branch information
Showing
5 changed files
with
212 additions
and
32 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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