Skip to content

Commit b2fdb11

Browse files
Update A87-grpc-metrics-xds-outlier-detection.md
1 parent 8315eec commit b2fdb11

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

A87-grpc-metrics-xds-outlier-detection.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,18 +12,18 @@ This document proposes some new metrics that will be added in gRPC for xDS Clien
1212

1313
## Background
1414

15-
A50: gRPC xDS Outlier Detection Support is a spec for gRPC to support xDS Outlier Detection. The current implementation only offers debug and trace logging in terms of visibility, which can be insufficient for understanding and diagnosing decision making in large-scale production systems. 
15+
[A50: gRPC xDS Outlier Detection Support](https://github.com/grpc/proposal/blob/master/A50-xds-outlier-detection.md) is a spec for gRPC to support xDS Outlier Detection. The current implementation only offers debug and trace logging in terms of visibility, which can be insufficient for understanding and diagnosing decision making in large-scale production systems. 
1616

1717
Using A79: Non-per-call Metrics Architecture, it is possible to add granular metrics to make visibility into outlier detection easy for service owners utilizing gRPC.
1818

1919
### Related proposals: 
20-
* A50: gRPC xDS Outlier Detection Support
21-
* A66: OpenTelemetry Metrics
22-
* A79: Non-per-call Metrics Architecture
20+
* [A50: gRPC xDS Outlier Detection Support](https://github.com/grpc/proposal/blob/master/A50-xds-outlier-detection.md)
21+
* [A66: OpenTelemetry Metrics](https://github.com/grpc/proposal/blob/master/A66-otel-stats.md)
22+
* [A79: Non-per-call Metrics Architecture](https://github.com/grpc/proposal/blob/master/A79-non-per-call-metrics-architecture.md)
2323

2424
## Proposal
2525

26-
A79’s non-per-call metrics architecture fits perfectly into the metrics reporting solution. We propose to aim for parity where appropriate with Envoy’s xDS implementation for metrics to be collected in gRPC
26+
[A79’s](https://github.com/grpc/proposal/blob/master/A79-non-per-call-metrics-architecture.md) non-per-call metrics architecture fits perfectly into the metrics reporting solution. We propose to aim for parity where appropriate with [Envoy’s Outlier Detection metric collection](https://www.envoyproxy.io/docs/envoy/latest/configuration/upstream/cluster_manager/cluster_stats#outlier-detection-statistics) to be collected in gRPC
2727

2828
Outlier Detection metrics will have the following labels:
2929

@@ -35,7 +35,7 @@ The following metrics will be exported:
3535

3636
| Name | Type | Unit | Labels | Description |
3737
| ------------- | ----- | ----- | ------- | ----------- |
38-
| grpc.xds_client.outlier_detection.ejections_enforced_total | Counter | {ejection} | grpc.target Total enforced ejections due to any outlier type |
38+
| grpc.xds_client.outlier_detection.ejections_enforced_total | Counter | {ejection} | grpc.target | Total enforced ejections due to any outlier type |
3939
| grpc.xds_client.outlier_detection.ejections_active | Gauge | {ejection} | grpc.target | Number of currently ejected hosts |
4040
| grpc.xds_client.outlier_detection.ejections_overflow | Counter | {ejection} | grpc.target | Number of ejections aborted due to max ejection percentage |
4141
| grpc.xds_client.outlier_detection.ejections_enforced_success_rate | Counter | {ejection} | grpc.target | Enforced success rate outlier ejections |

0 commit comments

Comments
 (0)