Notes on terminology

The words name, type, kind, metric, and resource appear in various combinations and contexts related to Cloud Monitoring, and the usages aren't always consistent. For example, here are some common patterns:

  • The term metric might be used, in different contexts, to refer to any of the following:

    • A general “something” to be measured
    • A metric type
    • A time series
    • A set of time series associated with a metric type
    • The Metric structure embedded in a TimeSeries structure
  • A string like storage.googleapis.com/api/request_count might be referred to as any of the following:

    • A metric
    • A metric name
    • A metric type
    • A metric type name
  • The string like gcs_bucket might be referred to as any of the following:

    • A resource name1
    • A monitored resource
    • A monitored-resource type
    • A monitored-resource name

1 The REST API reference material also makes frequent use of the term resource name, which usually has nothing to do with monitored resources. This term is described in more detail in Resource names.

This section provides some guidance on possibly confusing terminology.

Types and names

Descriptors for metric types and monitored resources have both names and types. It is common in casual usage to use the terms interchangeably.

For example, the string storage.googleapis.com/api/request_count is a metric type, though it is also referred to as a name or a type name.

If you look at the descriptor for this metric type, you see these two key-value pairs, name and type:

{
  "name": "projects/[PROJECT_ID]/metricDescriptors/storage.googleapis.com/api/request_count",
  ...
  "type": "storage.googleapis.com/api/request_count",
}

The type in a metric descriptor is a string that encodes information about the service generating the data (for example, storage.googleapis.com) and what's being measured (api/request_count).

In a metric descriptor, the value of the name is the fully-qualified version of metric type; the name value is the type value prefixed with this string:

projects/[PROJECT_ID]/metricDescriptors/

A similar pattern holds for monitored resources. The type is a label for some kind of resource, and the name consists of the type value prefixed with this string:

projects/[PROJECT_ID]/monitoredResourceDescriptors/

The following example corresponds to the api entry in the list of monitored resources:

{
  "type": "api",
  ...
  "name": "projects/[PROJECT_ID]/monitoredResourceDescriptors/api"
}

The value of name within a project is entirely predictable from the value of type, but they are not exactly the same thing. However, the terms are often used imprecisely in casual discussion.

Metric kind and value type

There are two other terms that can be confused with “metric type”:

  • Value type
  • Metric kind

These terms are not alternate terms for “metric type”.

“Value type” and “metric kind” describe the data collected. They are both related to the programming concept “datatype”.

  • The value type describes the individual values.
  • The metric kind describes how the values are related to each other.

See Metric kinds and types for details.

Resource names

The pattern of creating a name value by prefixing a string to a type (or other) value extends far beyond metric and montitored-resource types. It appears with almost anything that creates uniquely identifiable data. For example, both MetricDescriptor and AlertPolicy follow this pattern.

The value of the name field is often described in reference documentation as a “resource name”:

"Resource name" in API reference

Here are some examples of some structures that have resource names and how they are derived:

  • Metric descriptors: join the values of the prefix and the type field:
    • Prefix: projects/[PROJECT_ID]/metricDescriptors
    • type (sample): storage.googleapis.com/api/request_count
    • name: projects/[PROJECT_ID]/metricDescriptors/storage.googleapis.com/api/request_count
  • Monitored-resource descriptors: join the values of the prefix and the type field:
    • Prefix: projects/[PROJECT_ID]/monitoredResourceDescriptors
    • type (sample): api
    • name: projects/[PROJECT_ID]/monitoredResourceDescriptors/api
  • Alerting policies: join the values of the prefix and a generated ID
    • Prefix: projects/[PROJECT_ID]/alertPolicies
    • Alert-policy ID: a number generated when the policy was created
    • name: projects/[PROJECT_ID]/alertPolicies/[ALERT_POLICY_ID]

The term “resource name” refers to a resource in the hierarchy of a service's API, and isn't related to the concept of monitored resources in any way. For more information about resource names in the design of an API, see Resource names.