Stay organized with collections
Save and categorize content based on your preferences.
Metric types in Cloud Monitoring are classified into general groups,
based on the type of service that collects the data. This document provides
links to reference lists for each of these groups.
Metrics from Google Cloud services include:
Google Cloud metrics, for
Google Cloud services such as Compute Engine and BigQuery.
Metrics from agents, open-source, and third-party
applications include:
Metrics for the legacy Cloud Monitoring and Cloud Logging agents,
as well as the Ops Agent. With the exception of metrics from
third-party applications, the Ops Agent and the legacy agents share
many groups of metrics.
The tables in the metric-type lists are regenerated frequently and time-stamped.
The information listed for each metric type comes from
the Monitoring API MetricDescriptor
object for each metric type. For more information about how metric
types are described, see
Metrics, time series, and resources.
Launch stages
Each metric type has a launch stage that indicates its maturity. If specified,
the launch stage appears as a colored superscript after the metric type:
GA,
BETA,
ALPHA,
EARLY_ACCESS, or
DEPRECATED.
If no superscript appears, then the launch stage is unspecified.
For more information, see Product launch stages.
Metric types in the Alpha or Early Access launch stages might not appear in
the public lists of metrics. To get information about those metric types,
explicitly retrieve the set of metric descriptors from a Google Cloud
project that has been given permission to use the restricted metric types.
If you have permission to use restricted metric types, you can retrieve
the metric descriptors by using the
metricDescriptors.list method in the
Monitoring API. For more information, see
List metric descriptors.
Additional information: metadata
The description for each metric type includes information called metadata
about the metric. The metadata includes the following:
Sample Period: For metrics that are written periodically, this is the
time interval between consecutive data points, excluding data loss due to
errors. The period, if available, appears at the end of the description
text in a sentence of the form “Sampled every x
seconds.”
Latency: Data points older than this value are guaranteed to be
available to be read, excluding data loss due to errors. The delay does not
include any time spent waiting until the next sampling period. The delay, if
available, appears at the end of the description text in a sentence
of the form “After sampling, data is not visible for up to y
seconds.”
Resource hierarchy levels: Most metrics are collected only for
projects, but some metrics are also collected at the organization and folder
levels. If a level is not specified in the metadata, then the metric is
written at the project level.
Pricing
In general, Cloud Monitoring system metrics are free, and metrics
from external systems, agents, or applications are not. Billable metrics are
billed by either the number of bytes or the number of samples ingested.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Metrics list\n\nMetric types in Cloud Monitoring are classified into general groups,\nbased on the type of service that collects the data. This document provides\nlinks to reference lists for each of these groups.\n\nMetrics from Google Cloud services include:\n\n- [Google Cloud metrics](/monitoring/api/metrics_gcp), for Google Cloud services such as Compute Engine and BigQuery.\n- [Google Distributed Cloud metrics](/monitoring/api/metrics_anthos), for Google Distributed Cloud software only.\n- [Istio metrics](/monitoring/api/metrics_istio), for Istio on Google Kubernetes Engine.\n- [Kubernetes metrics](/monitoring/api/metrics_kubernetes), for Google Kubernetes Engine (GKE).\n\nMetrics from agents, open-source, and third-party applications include:\n\n\u003cbr /\u003e\n\n- Metrics for the legacy Cloud Monitoring and Cloud Logging agents,\n as well as the Ops Agent. With the exception of metrics from\n third-party applications, the Ops Agent and the legacy agents share\n many groups of metrics.\n\n - [Ops Agent metrics](/monitoring/api/metrics_opsagent), for VM instances\n running the Ops Agent.\n\n - [Legacy Monitoring and Logging agent\n metrics](/monitoring/api/metrics_agent), for VM instances running the\n legacy Monitoring and Logging agents.\n\n- [Knative metrics](/monitoring/api/metrics_knative), for Knative\n components.\n\n- [External metrics](/monitoring/api/metrics_other), for\n open-source and third-party applications.\n\nAbout the lists\n---------------\n\nThe tables in the metric-type lists are regenerated frequently and time-stamped.\nThe information listed for each metric type comes from\nthe Monitoring API [`MetricDescriptor`](/monitoring/api/ref_v3/rest/v3/projects.metricDescriptors#MetricDescriptor)\nobject for each metric type. For more information about how metric\ntypes are described, see\n[Metrics, time series, and resources](/monitoring/api/v3/metrics).\n\nLaunch stages\n-------------\n\nEach metric type has a launch stage that indicates its maturity. If specified,\nthe launch stage appears as a colored superscript after the metric type:\n^GA^,\n^BETA^,\n^ALPHA^,\n^EARLY_ACCESS^, or\n^DEPRECATED^.\nIf no superscript appears, then the launch stage is unspecified.\nFor more information, see [Product launch stages](/products#product-launch-stages).\n\nMetric types in the Alpha or Early Access launch stages might not appear in\nthe public lists of metrics. To get information about those metric types,\nexplicitly retrieve the set of metric descriptors from a Google Cloud\nproject that has been given permission to use the restricted metric types.\nIf you have permission to use restricted metric types, you can retrieve\nthe metric descriptors by using the\n[`metricDescriptors.list`](/monitoring/api/ref_v3/rest/v3/projects.metricDescriptors/list) method in the\nMonitoring API. For more information, see\n[List metric descriptors](/monitoring/custom-metrics/browsing-metrics#list-metric-descriptors).\n\nAdditional information: metadata\n--------------------------------\n\nThe description for each metric type includes information called *metadata*\nabout the metric. The metadata includes the following:\n\n- **Sample Period** : For metrics that are written periodically, this is the\n time interval between consecutive data points, excluding data loss due to\n errors. The period, if available, appears at the end of the description\n text in a sentence of the form *\"Sampled every* x\n *seconds.\"*\n\n- **Latency** : Data points older than this value are guaranteed to be\n available to be read, excluding data loss due to errors. The delay does not\n include any time spent waiting until the next sampling period. The delay, if\n available, appears at the end of the description text in a sentence\n of the form *\"After sampling, data is not visible for up to* y\n *seconds.\"*\n\n- **Resource hierarchy levels**: Most metrics are collected only for\n projects, but some metrics are also collected at the organization and folder\n levels. If a level is not specified in the metadata, then the metric is\n written at the project level.\n\nPricing\n-------\n\nIn general, Cloud Monitoring system metrics are free, and metrics\nfrom external systems, agents, or applications are not. Billable metrics are\nbilled by either the number of bytes or the number of samples ingested.\n\nFor more information, see the Cloud Monitoring sections of the [Google Cloud Observability pricing](https://cloud.google.com/stackdriver/pricing) page.\n\nGetting started\n---------------\n\n- For an introduction to the concepts and terminology used in the Cloud Monitoring metric model, see [Metrics, time series, and resources](/monitoring/api/v3/metrics).\n- To create your own metrics, see [Create user-defined metrics with the API](/monitoring/custom-metrics), [User-defined agent metrics](/monitoring/agent/custom-metrics-agent), and [Logs-based metrics](/logging/docs/view/logs_based_metrics).\n- To quickly see graphs of metric data, use the Metrics Explorer. For information about using this tool, see [Create charts with Metrics Explorer](/monitoring/charts/metrics-explorer)."]]