The following table lists the infrastructure resources that are integrated with Application Monitoring. When these resources are registered as an App Hub service or workload, the telemetry that the resources generate includes application-specific labels. This telemetry includes platform and audit log entries, metric data, and trace data. For a list of services and workloads that are integrated with App Hub, see App Hub supported resources.
Label format depends on the telemetry type and how the data is
generated. For example, log entries that contain application-specific labels
contain a JSON element of type apphub. For metric data, application
information is attached to the time series either with system metadata labels
or with metric labels. How the metric data is generated determines the
exact labels. For more information, see
application-specific labels.
Some infrastructure can generate one or more of the following golden signals:
- 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
The Notes 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 to metric data or to spans. | |
| Cloud Run jobs (Regional) |
|
Application labels aren't attached to log entries. |
| 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) |
|
|
| Firestore databases (Regional) |
|
Application labels aren't attached to spans. |
| Kubernetes CronJobs (Regional and zonal) |
To learn how to run Cron Jobs in GKE, see About 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, see About 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, only forwarding rules an backend services are integrated with App Hub. Application labels aren't attached to spans. |
| Memorystore for Redis clusters (Regional) |
|
Application labels aren't attached to log entries or to spans. |
| Memorystore for Redis instances (Regional) |
Application labels aren't attached to metric 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. |
| Spanner databases (Global and regional) |
Application labels aren't attached to metric data or to spans. | |
| Spanner instances (Global and regional) |
|
Application labels aren't attached to spans. |