Which approach delivers real time alerts for Cloud Spanner transaction failures and also reflects overall application health?

Question

Options

• AError Reporting notifications
• BCloud Monitoring alerts on Spanner transaction failure metrics
• CCloud Logging logs based metric with alerting

• A
  4% (1)
• B
  86% (24)
• C
  11% (3)

Explanation

Cloud Monitoring has native, pre-built metrics for Cloud Spanner that include transaction abort counts, transaction commit latency, and error rates. Alerting policies on these metrics fire in near-real time when thresholds are breached, directly reflecting transaction failure behavior. Because these metrics are derived from the Spanner infrastructure itself (not just application logs), they also correlate with overall database health, giving a holistic view of application behavior. Option A (Error Reporting) aggregates application-level stack traces and exceptions; it depends on the application explicitly reporting errors and may miss failures that Spanner handles internally before returning an error to the client. Option C (logs-based metrics) can work but introduces additional latency because log ingestion and metric computation add processing time, and it requires custom configuration to extract the right signals from unstructured log data.

No community discussion yet for this question.