Docs » Monitor services and hosts in Splunk Infrastructure Monitoring » Monitor Google Cloud Platform » Google Cloud Platform metadata

Google Cloud Platform metadata πŸ”—

The GCP integration queries the GCP API for metadata about the monitored resources. You can filter and group metrics by this metadata in charts, or in the Infrastructure Navigator.

  • Metadata that are common to all services within a project (project-level metadata) are put on properties of project_id dimension.

  • Metadata that are service-specific (service-level metadata) are put on properties of the gcp_id dimension.

Project-level metadata πŸ”—

See the metadata synced at a project level:

GCP name

Custom property

Description

creationTimestamp

gcp_project_creation_time

Time project was created (for example, Thu Oct 19 18:16:25 UTC 2017)

Labels *

gcp_project_label_<name-of-label> (if user has labels)

All project-wide labels except for signalfx-id

name

gcp_project_name

Human readable project name

project_number

gcp_project_number

Project_number given by GCP

status

gcp_project_status

Project status (e.g. ACTIVE, DELETE_IN_PROGRESS, DELETE_REQUESTED)

* Labels is a list of key value pairs in GCP. Therefore, if GCP has [key1:label01, key2:label02] as the labels property, Infrastructure Monitoring has two properties: gcp_project_label_key1 and gcp_project_label_key2.

Service-level metadata πŸ”—

See the metadata synced at a service level:

Compute Engine πŸ”—

For Google Cloud Platform Compute Engine instances, Infrastructure Monitoring gets a subset of metadata about the instance, as well as custom metadata specified by the user at an instance level.

Note

The Compute Engine instance metadata table includes two custom properties that are now deprecated, as well as information about which properties replace the deprecated properties.

Compute Engine instance metadata

GCP name

Custom property

Description

scheduling.automaticRestart

gcp_auto_restart

Whether the instance should be automatically restarted if it is terminated by Compute Engine (not terminated by a user)

scheduling.onHostMaintenance

gcp_behavior_on_maintenance

Maintenance behavior for the instance

scheduling.preemptible

gcp_preemptibility

True if the instance is preemptible; otherwise false

cpuPlatform

gcp_cpu_platform

CPU platform used by this instance

CPU

gcp_cpus

Number of virtual CPUs that are available to the instance

creationTimestamp

gcp_creation_time

Time when the instance was created, (for example, Thu Oct 19 18:16:25 UTC 2017)

description

gcp_description

Description of this instance

disks[].licenses[] *

gcp_image_license

License corresponding to the disks used by the instance

canIpForward

gcp_ip_forward

Whether to allow this instance to send and receive packets with non-matching destination or source IPs

machineType

gcp_machine_type

Type of gcp machine to which this instance corresponds

memory

gcp_memory

Amount of physical memory available to the instance, defined in MB

metadata **

gcp_metadata_<metadata-key>

Custom metadata key for the instance (generated based on includelisted properties specified when completing the integration in Splunk Infrastructure Monitoringx)

status

gcp_status

String containing instance status and status code, for example Code=2, Status=RUNNING. This property is now deprecated, and won’t contain new statuses introduced by GCP such as REPAIRING or SUSPENDING. Use gcp_instance_status instead.

status

gcp_instance_status

Status of the instance, for example RUNNING or STAGING.

self_link

gcp_self_link

Instance self link as reported by GCP

standard_id

gcp_standard_id

Instance ID in a format enforced by Splunk Observability Cloud, for example https://compute.googleapis.com/compute/v1/projects/testProject/zones/us-central1-a/instances/testInstance. This property is now deprecated. Use gcp_self_link instead.

* There is not a one-to-one mapping between the gcp_image_license property to one in GCP because the property value is derived from the licenses of the disks associated with the compute instance.

** Labels is a list of key value pairs in GCP. Therefore, if GCP has [key1:label01, key2:label02] as the labels property, Infrastructure Monitoring has two properties: gcp_project_label_key1 and gcp_project_label_key2.

For detailed information on properties, see Google Cloud documentation.

Kubernetes Engine πŸ”—

GKE syncs properties for the following resources:

k8s_container

GCP name

Custom property

Description

cluster_name

gcp_cluster_name

Cluster name

namespace_name

gcp_namespace_name

Name of the pod’s namespace

pod_name

gcp_pod_name

Pod name

container_name

gcp_container_name

Container name

k8s_node

GCP name

Custom property

Description

cluster_name

gcp_cluster_name

Cluster name

node_name

gcp_node_name

Node name

k8s_pod

GCP name

Custom property

Description

cluster_name

gcp_cluster_name

Cluster name

namespace_name

gcp_namespace_name

Name of the pod’s namespace

pod_name

gcp_pod_name

Pod name

Storage Bucket πŸ”—

Storage buckets sync the following properties:

GCP name

Custom property

Description

creationTimestamp

gcp_creation_time

Time at which the bucket was created, (for example, Thu Oct 19 18:16:25 UTC 2017)

Labels *

gcp_label_<name-of-label> (if user has labels)

User-specified labels

Storage class

gcp_storage_class

Bucket’s storage class, such as coldline

* Labels is a list of key value pairs in GCP. Therefore, if GCP has [key1:label01, key2:label02] as the labels property, Infrastructure Monitoring has two properties: gcp_project_label_key1 and gcp_project_label_key2.

Spanner πŸ”—

Spanner instances currently sync the following properties:

GCP name

Custom property

Description

state

gcp_state

State of the spanner instance (e.g. CREATING, READY)

Labels *

gcp_label_<name-of-label> (if user has labels)

User-specified labels

* Labels is a list of key value pairs in GCP. Therefore, if GCP has [key1:label01, key2:label02] as the labels property, Infrastructure Monitoring has two properties: gcp_project_label_key1 and gcp_project_label_key2.