LogoLogo
Log in|Playground
  • Welcome
    • Introduction
    • FAQ
  • Capabilities
    • Log Management
    • Infrastructure Monitoring
    • Application Performance Monitoring (APM)
      • Application Metrics
      • Traces
      • Supported Technologies
    • Real User Monitoring (RUM)
  • Getting Started
    • Requirements
      • Kubernetes requirements
      • Kernel requirements for eBPF sensor
      • CPU architectures
      • ClickHouse resources
    • Installation & updating
    • Connect Linux hosts
    • Connect RUM
    • 5 quick steps to get you started
    • groundcover MCP
  • Use groundcover
    • Monitors
      • Create a new Monitor
      • Issues page
      • Monitor List page
      • Silences page
      • Monitor Catalog page
      • Monitor YAML structure
      • Embedded Grafana Alerts
        • Create a Grafana alert
    • Dashboards
      • Create a dashboard
      • Embedded Grafana Dashboards
        • Create a Grafana dashboard
        • Build alerts & dashboards with Grafana Terraform provider
        • Using groundcover datasources in a Self-hosted Grafana
    • Insights
    • Explore & Monitors query builder
    • Workflows
      • Create a new Workflow
      • Workflow Examples
      • Alert Structure
    • Search & Filter
    • Issues
    • Role-Based Access Control (RBAC)
    • Service Accounts
    • API Keys
    • APIs
    • Log Patterns
    • Drilldown
    • Scraping custom metrics
      • Operator based metrics
      • kube-state-metrics
      • cadvisor metrics
    • Backup & Restore Metrics
    • Metrics & Labels
    • Add custom environment labels
    • Configuring Pipelines
      • Writing Remap Transforms
      • Logs Pipeline Examples
      • Traces Pipeline Examples
      • Logs to Events Pipeline Examples
      • Logs/Traces Sensitive Data Obfuscation
      • Sensitive Data Obfuscation using OTTL
      • Log Filtering using OTTL
    • Querying your groundcover data
      • Query your logs
        • Example queries
        • Logs alerting
      • Query your metrics
      • Querying you data using an API
      • Using KEDA autoscaler with groundcover
  • Log Parsing with OpenTelemetry Pipelines
  • Log and Trace Correlation
  • RUM
  • Customization
    • Customize deployment
      • Agents in host network mode
      • API Key Secret
      • Argo CD
      • On-premise deployment
      • Quay.io registry
      • Configuring sensor deployment coverage
      • Enabling SSL Tracing in Java Applications
    • Customize usage
      • Filtering Kubernetes entities
      • Custom data retention
      • Sensitive data obfuscation
      • Custom storage
      • Custom logs collection
      • Custom labels and annotations
        • Enrich logs and traces with pod labels & annotations
        • Enrich metrics with node labels
      • Disable tracing for specific protocols
      • Tuning resources
      • Controlling the eBPF sampling mechanism
  • Integrations
    • Overview
    • Workflow Integrations
      • Slack Webhook Integration
      • Opsgenie Integration
      • Webhook Integration
        • Incident.io
      • PagerDuty Integration
      • Jira Webhook Integration
      • Send groundcover Alerts to Email via Zapier
    • Data sources
      • OpenTelemetry
        • Traces & Logs
        • Metrics
      • Istio
      • AWS
        • Ingest CloudWatch Metrics
        • Ingest CloudWatch Logs
        • Ingest Logs Stored on S3
        • Integrate CloudWatch Grafana Datasource
      • GCP
        • Ingest Google Cloud Monitoring Metrics
        • Stream Logs using Pub/Sub
        • Integrate Google Cloud Monitoring Grafana Datasource
      • Azure
        • Ingest Azure Monitor Metrics
      • DataDog
        • Traces
        • Metrics
      • FluentBit
      • Fluentd
      • JSON Logs
    • 3rd-party metrics
      • ActiveMQ
      • Aerospike
      • Cassandra
      • CloudFlare
      • Consul
      • CoreDNS
      • Etcd
      • HAProxy
      • Harbor
      • JMeter
      • K6
      • Loki
      • Nginx
      • Pi-hole
      • Postfix
      • RabbitMQ
      • Redpanda
      • SNMP
      • Solr
      • Tomcat
      • Traefik
      • Varnish
      • Vertica
      • Zabbix
    • Source control (Gitlab/Github)
  • Architecture
    • Overview
    • inCloud Managed
      • Setup inCloud Managed with AWS
        • AWS PrivateLink Setup
        • EKS add-on
      • Setup inCloud Managed with GCP
      • Setup inCloud Managed with Azure
      • High Availability
      • Disaster Recovery
      • Ingestion Endpoints
      • Deploying in Sensor-Only mode
    • Security considerations
      • Okta SSO - onboarding
    • Service endpoints inside the cluster
  • Product Updates
    • What's new?
    • Earlier updates
      • 2025
        • Mar 2025
        • Feb 2025
        • Jan 2025
      • 2024
        • Dec 2024
        • Nov 2024
        • Oct 2024
        • Sep 2024
        • Aug 2024
        • July 2024
        • May 2024
        • Apr 2024
        • Mar 2024
        • Feb 2024
        • Jan 2024
      • 2023
        • Dec 2023
        • Nov 2023
        • Oct 2023
Powered by GitBook
On this page
  • Things to know
  • Ingestion interval
  • Data storage
  • Supported services
  • Setting up the integration
  • Create a Service Account and Assign Permissions
  • Share details with groundcover
Export as PDF
  1. Integrations
  2. Data sources
  3. GCP

Ingest Google Cloud Monitoring Metrics

Last updated 2 months ago

groundcover supports ingesting Google Cloud Monitoring Metrics directly into our platform, allowing you to visualize them using dashboards and create alerts.

Things to know

Ingestion interval

The integration pulls data from Google Cloud Monitoring every five minutes.

Data storage

Data fetched is stored in the Victoria Metrics database, meaning metrics are queried via the Google Cloud Monitoring API only one time per data point.

Supported services

groundcover supports ingestion of every GCP service listed in the GCP . All metrics listed under that service will be fetched.

The list is also available below:

List of supported services
actions
aiplatform
alloydb
apigateway
apigee
appengine
apphub
artifactregistry
autoscaler
backupdr
baremetalsolution
bigquery
bigquerybiengine
bigquerydatatransfer
bigquerystorage
bigtable
billingbudgets
blockchainnodeengine
certificatemanager
chronicle
cloudaicompanion
cloudbuild
clouddeploy
cloudfunctions
cloudkms
cloudsql
cloudtasks
cloudtrace
composer
compute
connectors
contactcenterinsights
container
dataflow
datamigration
dataplex
dataproc
datastore
datastream
dbinsights
dialogflow
discoveryengine
displayvideo
dlp
dns
earthengine
edgecache
edgecontainer
eventarc
file
firebaseappcheck
firebaseapphosting
firebaseauth
firebasedatabase
firebasedataconnect
firebaseextensions
firebasehosting
firebasestorage
firestore
firewallinsights
fleetengine
gkebackup
healthcare
iam
identitytoolkit
ids
integrations
interconnect
livestream
loadbalancing
logging
managedflink
managedidentities
managedkafka
maps
memcache
memorystore
metastore
ml
monitoring
netapp
networkconnectivity
networking
networksecurity
networkservices
oracledatabase
osconfig
parallelstore
privateca
pubsub
pubsublite
recaptchaenterprise
recommendationengine
redis
retail
router
run
serviceruntime
spanner
storage
storagetransfer
telcoautomation
tpu
trafficdirector
transferappliance
translationhub
videostitcher
visionai
vpcaccess
vpn
workflows

Setting up the integration

The following steps requires the details of dedicated service account set up the integration - marked below as <integrations-sa>.

Make sure it has been provided to you by the groundcover team

Create a Service Account and Assign Permissions

  1. Go to IAM & Admin in GCP Console

  2. Navigate to IAM & Admin → Service Accounts.

  3. Create a New Service Account

    • Click on Create Service Account.

    • Provide a name and description for the service account.

    • Click Create & Continue.

    • In the Grant this service account access to the project step, search for and select Monitoring Viewer (roles/monitoring.viewer).

    • Click Continue → Done.

  4. Grant service account impersonation access

    • Click on the newly created service account → Permissions → View by Principals → Grant Access

    • In the Add principals → New principal section enter the <integrations-sa> provided to you.

    • In the Assign roles → Role section choose Service Account Token Creator

    • Click Save

Share details with groundcover

Share the following details with the groundcover team to complete the integration:

  1. The details of the service account created above

  2. The list of services you wish to ingest metrics from

  3. The region that hosts the account you wish to ingest metrics from

  4. The list of project ids you wish to ingest metrics from

docs