Application Monitoring supported infrastructure Stay organized with collections Save and categorize content based on your preferences.
The dashboards that Application Monitoring creates display logand metric data, including the following golden signals, when that data includesapplication-specific labels:
- Traffic: Incoming request rates on the service or workload over the selected time period.
- Server error rate: Average percentage of incoming requests that generate or map to 5xx HTTP response codes over the selected time period.
- P95 latency: 95th percentile of latency for a request served over the selected time period, in milliseconds.
- Saturation: Measures how full your service or workload is. For example, for managed instance groups (MIGs), Cloud Run, and Google Kubernetes Engine deployments, this field shows the CPU utilization.
Supported infrastructure resources
TheNotes column lists details about which golden signals are supported.This column also lists limitations.
| Infrastructure resources | Golden signals | Notes and limitations |
|---|---|---|
| AlloyDB for PostgreSQL clusters (Regional) | Application labels aren't attached to spans. | |
| AlloyDB for PostgreSQL instances (Regional) |
| Application labels aren't attached to spans. |
| Bigtable clusters (Regional) |
| Application labels aren't attached to spans. |
| Bigtable instances (Regional) | Application labels aren't attached tometric data or to spans. | |
| Cloud Run jobs (Regional) |
| |
| Cloud Run services and functions (Regional) |
| Only trace spans generated by instrumented workloads contain application labels. Only customer-instrumented workloads running within Cloud Run generate golden signals. |
| Cloud Logging log buckets (Global and regional) | Only audit logs contain application labels. | |
| Cloud SQL instances (Regional) |
| Application labels aren't attached to spans. |
| Cloud Storage buckets (Regional and multi-regional) |
| Application labels aren't attached to spans. |
| Compute Engine MIGs (Regional and zonal) |
| |
| Dataproc Metastore service (Regional and multi-regional) |
| Application labels aren't attached to spans. For general information, seeDataproc Metastore overview. |
| Cloud Deploy delivery pipelines (Regional) | Application labels aren't attached to spans. | |
| Firestore databases (Regional) |
| Application labels aren't attached to spans. |
| Kubernetes CronJobs (Regional and zonal) | To learn how to run Cron Jobs in GKE, seeAbout CronJobs in GKE. | |
| Kubernetes DaemonSets (Regional and zonal) |
| |
| Kubernetes Deployments (Regional and zonal) |
| |
| Kubernetes StatefulSets (Regional and zonal) |
| To learn how to use a StatefulSet or deploy a stateful application, seeAbout StatefulSets in Google Kubernetes Engine. |
| Layer 7 external and internal Application Load Balancers with HTTP or HTTPS traffic (Global and regional) |
| For Application Load Balancers, onlyforwarding rules anbackend services are integrated with App Hub. Application labels aren't attached to spans. |
| Memorystore for Redis clusters (Regional) |
| Application labels aren't attached tolog entries or to spans. |
| Memorystore for Redis instances (Regional) | Application labels aren't attached tometric data or to spans. | |
| Pub/Sub topics (Global) |
| Application labels aren't attached to spans. |
| Pub/Sub subscription (Global) |
| Application labels aren't attached to spans. |
| Secret Manager secrets (Global and regional) | Application labels aren't attached to spans. | |
| Spanner databases (Global and regional) | Application labels aren't attached tometric data or to spans. | |
| Spanner instances (Global and regional) |
| Application labels aren't attached to spans. |
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.