feat(spanner): Switch to using builtin open telemetry for EEF#14193
feat(spanner): Switch to using builtin open telemetry for EEF#14193rahul2393 merged 2 commits intogoogleapis:mainfrom
Conversation
There was a problem hiding this comment.
Code Review
The pull request successfully switches the EEF (Enhanced Error Handling) metrics to use the built-in OpenTelemetry framework. The changes involve updating the client configuration to conditionally set the meter provider, defining new constants for metric names and labels, and configuring OpenTelemetry views to correctly filter and aggregate EEF-related metrics. The monitoring exporter has also been updated to handle the new gRPC-GCP meter name and apply specific attribute filtering for EEF metrics. The implementation appears robust and correctly aligns with the stated objective. No issues of medium, high, or critical severity were identified in this review.
|
@kinsaurralde please change the first commit message |
PR created by the Librarian CLI to initialize a release. Merging this PR will auto trigger a release. Librarian Version: v0.10.1 Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/librarian-go@sha256:b04b076f5eedbb5546bd6fc1404969dd3698c8b19c0f34ae815a84ae735a606a <details><summary>spanner: v1.90.0</summary> ## [v1.90.0](spanner/v1.89.0...spanner/v1.90.0) (2026-04-14) ### Features * feat(spanner): add EnableDirectAccess field to ClientConfig (#14287) ([6adf5b7](6adf5b7)) * feat(spanner): Switch to using builtin open telemetry for EEF (#14193)([751febd](751febd)) * feat(spanner): complete location-aware routing resilience and observability (#14418 ) ([77aa4df](77aa4df)) ### Bug Fixes * fix(spanner): set gauge metric start time to match end time (#14289) ([e0760b5](e0760b5)) * fix(spanner): update DirectPath detection logic to use ALTS credentials(#14288)([3cd5716](3cd5716)) </details>
Switching to built in open telemetry since the eef metrics are internal metrics