Load balancing metrics

You can monitor the performance and health of your Google Cloud load-balanced applications and services using metrics provided by Cloud Monitoring. These metrics represent collections of measurements that help you maintain optimal operations. In Cloud Monitoring, each service or component under observation is called a monitored resource.

Use the following resources to find details about supported metric types, units used, and their metadata:

  • For a general explanation of the entries in the tables, see Metric types.

  • For information about the units used in the metric lists, see the unit field in the MetricDescriptor reference.

  • For information about statements of the form “Sampled every x seconds” and “After sampling, data is not visible for up to y seconds”, see Additional information: metadata.

  • For a set of complete, current lists of supported metric types, see Metrics list.

  • For pricing information, see Monitoring pricing.

The following table maps metric path prefixes to the load balancer types:

Metric path Load balancer
https/ Global external Application Load Balancer

Classic Application Load Balancer
https/external/regional Regional external Application Load Balancer
https/internal/ Cross-region internal Application Load Balancer

Regional internal Application Load Balancer
l3/external/ External passthrough Network Load Balancer
l3/internal/ Internal passthrough Network Load Balancer
tcp_ssl_proxy/ Classic proxy Network Load Balancer
l4_proxy/ Global external proxy Network Load Balancer

Cross-region internal proxy Network Load Balancer

Regional internal proxy Network Load Balancer

Regional external proxy Network Load Balancer

The "metric type" strings in this table must be prefixed with loadbalancing.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
application_lb/backend_latencies BETA(project)
Backend latencies
DELTADISTRIBUTIONms
gce_backend_service
A distribution of the latency calculated from when the request was sent by the Application Load Balancer proxy to the backend until the proxy received from the backend the last byte of response. For Service Extensions, this value represents the sum of latencies of each ProcessingRequest/ProcessingResponse pair between the load balancer and the extension backend.
protocol: Protocol used by the client: 'HTTP/1.0', 'HTTP/1.1', 'HTTP/2.0', 'QUIC/HTTP/2.0' or 'UNKNOWN'.
response_code: (INT64) HTTP response code.
response_code_class: (INT64) HTTP response code class: 200, 300, 400, 500 or 0 for none.
cache_result: Cache result for serving HTTP request by proxy: 'HIT', 'MISS', 'DISABLED' or 'UNKNOWN'.
matcher_type: The type of rule matched for the request: 'PATH_MATCHER' or 'DEFAULT_MATCH'. 'DEFAULT_MATCH' indicates that the default route rule or action was matched to the request.
matcher_name: Matched rule for the request. Label value is based on matcher_type. PATH_MATCHER type will be the name of the path matcher. DEFAULT_MATCH types will be empty.
matched_path: The prefix, exact, regex, or template URL path matcher that matched the request. 'UNMATCHED' for the sink default rule.
load_balancing_scheme: Load balancing scheme used by the Application Load Balancer: 'EXTERNAL_MANAGED' or 'INTERNAL_MANAGED'.
client_country: Country of the client where the traffic originated from, such as 'United States' or 'Germany'.
proxy_continent: Continent of the proxy where the traffic originated from, such as 'North America' or 'Europe'.
application_lb/backend_request_bytes_count BETA