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
Description
After upgrading to Spanner client library versions >v1.71.0, our application began failing with permission errors (monitoring.timeSeries.create denied) in production. This is caused by the new native metrics collection being enabled by default, which requires the monitoring.metricWriter role. While disabling via DisableNativeMetrics: true resolves the issue, we believe this behavior introduces an unexpected breaking change and poses risks for existing users.
Proposed Fixes
Change Default to DisableNativeMetrics: true:
Revert to disabling metrics by default to avoid breaking existing deployments.
Environment
Library Version: v1.71.0+
GCP Environment: Cloud Run / GKE / etc.
Permissions: Service account lacks monitoring.metricWriter.
The text was updated successfully, but these errors were encountered:
codyoss
changed the title
Breaking Change: Native Metrics Enabled by Default in v1.71.0+ Causes Permission Errors
spanner: Native Metrics Enabled by Default in v1.71.0+ Causes Permission Errors
Mar 3, 2025
Description
After upgrading to Spanner client library versions >v1.71.0, our application began failing with permission errors (monitoring.timeSeries.create denied) in production. This is caused by the new native metrics collection being enabled by default, which requires the monitoring.metricWriter role. While disabling via DisableNativeMetrics: true resolves the issue, we believe this behavior introduces an unexpected breaking change and poses risks for existing users.
Proposed Fixes
Change Default to DisableNativeMetrics: true:
Revert to disabling metrics by default to avoid breaking existing deployments.
Environment
Library Version: v1.71.0+
GCP Environment: Cloud Run / GKE / etc.
Permissions: Service account lacks monitoring.metricWriter.
The text was updated successfully, but these errors were encountered: