Metrics list

Metric types in Stackdriver Monitoring are classified into general groups, based on the type of service that collects the data. This page provides links to reference lists for each of these groups:

The metric-type lists are rebuilt frequently and time-stamped, so you know how current they are. The information listed for each metric type comes from the Monitoring API MetricDescriptor object for each metric type. For more information on how metric types are described, see Metrics, time series, and resources.

Stackdriver charges for some metrics. For more information, see Pricing: Monitoring details and Workspaces.

Additional information: metadata

The entry for each metric type might include additional information, called metadata, about the metric. This data is presently available for GCP, Agent, AWS, and some Anthos metrics. The metadata shown with entries in the table includes the following:

  • Launch stage: The launch stage of the metric type, given by a colored tag that precedes the display name: GA, BETA, ALPHA, EARLY_ACCESS, or DEPRECATED. If no tag appears, then the launch stage is unspecified.

    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 Platform 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. See Listing metric descriptors for more information.

  • 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.”*

  • Ingest Delay: 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.”*

Getting started

Was this page helpful? Let us know how we did:

Send feedback about...

Stackdriver Monitoring
Need help? Visit our support page.