Application Monitoring supported services and workloads

The following table lists services and workloads that are integrated with App Hub and that generate metric data with application-specific labels. This document doesn't list all services and workloads that are integrated with App Hub. For a complete list of integrations, 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 services and workloads 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 services

The following table lists services that are integrated with Application Monitoring. In general, platform log entries, audit log entries, and metric data for these services contain application-specific labels. The Notes column lists details about which golden signals are supported. This column also lists limitations.

Services Notes
Bigtable clusters
(Regional)		 Available golden signals:

Log entries don't include application labels.
Bigtable instances
(Regional)

Metric data doesn't include application labels.

Platform log entries don't include application labels.
Cloud Run services
(Regional)		 Available golden signals:
Cloud SQL instances
(Regional)		 Available golden signals:
Cloud Storage buckets
(Regional and multi-regional)		 Available golden signals:
  • Traffic: api/request_count
  • Server error rate: Ratio of requests with a response status that indicates an error to the total number of requests. The following status values indicate an error:
    • DATA_LOSS
    • DEADLINE_EXCEEDED
    • INTERNAL
    • UNAVAILABLE
    • UNIMPLEMENTED
    • UNKNOWN

Platform log entries don't include application labels.
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.

Available golden signals:

  • Traffic: Based on a Cloud Load Balancing metric type that records the request count, like https/request_count. The configuration of the Cloud Load Balancing determines the actual metric.
  • Server error rate: The ratio of the number of requests with a response status of 5xx to the total number of requests.
  • P95 latency: Based on a Cloud Load Balancing metric type that records total latencies, like https/total_latencies. The configuration of the Cloud Load Balancing determines the actual metric.

Platform log entries don't include application labels.
Memorystore for Redis clusters
(Regional)		 Available golden signals:

Platform log entries don't include application labels.
Pub/Sub topics
(Global)		 Available golden signals:
  • Traffic: topic/send_request_count
  • Server error rate: The ratio of the number of requests with a response code of internal to the total number of requests.
Spanner instances
(Global and regional)		 Available golden signals:
  • Traffic: api/api_request_count
  • Server error rate: Ratio of requests with a response status that indicates an error to the total number of requests. The following status values indicate an error:
    • data_loss
    • deadline_exceeded
    • internal
    • unavailable
    • unimplemented
    • unknown
  • Saturation: instance/cpu/utilization

Platform log entries don't include application labels.

Supported workloads

The following table lists workloads that are integrated with Application Monitoring. In general, platform log entries, audit log entries, and metric data for these workloads contain application-specific labels. The Notes column lists details about which golden signals are supported. This column also lists limitations.

Workloads Notes
Cloud Run jobs
(Regional)		 Available golden signals:

Platform log entries don't include application labels.
Compute Engine MIGs
(Regional and zonal)		 Available golden signals:
Kubernetes CronJobs
(Regional and zonal)

No golden signals are available.

To learn how to run Cron Jobs in GKE, see About CronJobs in GKE.
Kubernetes DaemonSets
(Regional and zonal)		 Available golden signals:
Kubernetes Deployments
(Regional and zonal)		 Available golden signals:
Kubernetes StatefulSets
(Regional and zonal)		 Available golden signals:

To learn how to use a StatefulSet or deploy a stateful application, see About StatefulSets in Google Kubernetes Engine.