You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/metrics/README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -4,14 +4,14 @@ The custom metric exporter, as defined in [spanner-metrics-exporter.ts](./spanne
4
4
## Filtering Criteria
5
5
The exporter filters metrics based on the following conditions, utilizing values defined in [constants.ts](./constants.ts):
6
6
7
-
* Metrics with a scope set to `gax-nodejs`.
7
+
* Metrics with a scope set to `spanner-nodejs`.
8
8
* Metrics with one of the following predefined names:
9
9
*`attempt_latencies`
10
10
*`attempt_count`
11
11
*`operation_latencies`
12
12
*`operation_count`
13
13
*`gfe_latency`
14
-
*`gfe_missing_header_count`
14
+
*`gfe_connectivity_error_count`
15
15
16
16
## Service Endpoint
17
17
The exporter sends metrics to the Google Cloud Monitoring [service endpoint](https://cloud.google.com/python/docs/reference/monitoring/latest/google.cloud.monitoring_v3.services.metric_service.MetricServiceClient#google_cloud_monitoring_v3_services_metric_service_MetricServiceClient_create_service_time_series), distinct from the regular client endpoint. This service endpoint operates under a different quota limit than the user endpoint and features an additional server-side filter that only permits a predefined set of metrics to pass through.
`Need monitoring metric writer permission on project ${this._projectId}. Follow https://cloud.google.com/spanner/docs/view-manage-client-side-metrics#access-client-side-metrics to set up permissions`
0 commit comments