Skip to content

feat(spanner): Switch to using builtin open telemetry for EEF#14193

Merged
rahul2393 merged 2 commits intogoogleapis:mainfrom
kinsaurralde:eef_metrics_builtin
Apr 2, 2026
Merged

feat(spanner): Switch to using builtin open telemetry for EEF#14193
rahul2393 merged 2 commits intogoogleapis:mainfrom
kinsaurralde:eef_metrics_builtin

Conversation

@kinsaurralde
Copy link
Copy Markdown
Contributor

Switching to built in open telemetry since the eef metrics are internal metrics

@kinsaurralde kinsaurralde requested review from a team as code owners March 17, 2026 23:51
@product-auto-label product-auto-label Bot added the api: spanner Issues related to the Spanner API. label Mar 17, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@rahul2393
Copy link
Copy Markdown
Contributor

rahul2393 commented Mar 20, 2026

@kinsaurralde please change the first commit message

@kinsaurralde kinsaurralde changed the title feat(spanner): Switch Eef metrics to using built in open telemetry feat(spanner): Switch to using builtin open telemetry for EEF Mar 20, 2026
@rahul2393 rahul2393 added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 25, 2026
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 25, 2026
@rahul2393 rahul2393 requested a review from sakthivelmanii April 2, 2026 05:42
@rahul2393 rahul2393 merged commit 751febd into googleapis:main Apr 2, 2026
10 of 11 checks passed
rahul2393 added a commit that referenced this pull request Apr 14, 2026
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: spanner Issues related to the Spanner API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants