Metrics and alerting policy filters

This document provides an overview of the metrics generated by Database Center. It also describes how you can use filters to restrict data that is charted or monitored by alerting policies. To help you identify and troubleshoot performance issues for database products such as Cloud SQL, AlloyDB for PostgreSQL, and Spanner, create custom dashboards that display useful metrics and information about your alerting policies.

Database Center metric types

This section lists the metric types that are generated by Database Center.

The "metric type" strings in this table must be prefixed with databasecenter.googleapis.com/. That prefix has been omitted from the entries in the table. When querying a label, use the metric.labels. prefix; for example, metric.labels.LABEL="VALUE".

Metric type Launch stage(Resource hierarchy levels)
Display name
Kind, Type, Unit
Monitored resources
Description
Labels
resource/new_resource_count BETA(project)
New database resources
CUMULATIVEINT641
databasecenter.googleapis.com/Resource
Number of new database resources.
product: Type of product.
engine: Type of engine.
version: Version of the product.
resource/new_signal_count BETA(project)
New database signals
CUMULATIVEINT641
databasecenter.googleapis.com/Resource
Number of signals generated for resources.
issue_type: Type of signal.

Table generated at 2026-09-17 19:38:45 UTC.

About metric filters

When you create charts or alerting policies, you can add filters to restrict the metric data that's charted or monitored. For example, you might add a filter so a chart displays data only for a specific resource. Your charts and notifications from alerting policies can help you troubleshoot issues. They can also help you gain deeper insights into the health of your database fleet.

A filter is composed of a label key and a label value. For example, a label key might be resource_container and the label value is a specific resource container. You can filter metric data by metric labels and by resource labels: