Google Cloud Integration
Connect your entire GCP environment to TigerOps in minutes. Monitor GKE clusters, Cloud Run services, BigQuery pipelines, Pub/Sub queues, and 30+ services with AI-powered anomaly detection.
How It Works
Create a Service Account
In GCP IAM, create a service account for TigerOps and assign the Monitoring Viewer and Cloud Asset Viewer roles. No write permissions required.
Download the JSON Key
Generate a JSON service account key and paste it into the TigerOps GCP integration panel. Alternatively, use Workload Identity Federation for keyless auth.
Select Projects
Choose which GCP projects to monitor. TigerOps auto-discovers resources across all enabled APIs and starts collecting metrics from every selected project.
AI Baseline & Alerting
The AI SRE builds behavioral baselines per service within minutes. Anomaly detection and automated runbooks activate as soon as enough data is collected.
What You Get Out of the Box
GKE Cluster Observability
Node, pod, namespace, and workload-level metrics for all GKE clusters. Correlated with application traces and logs from workloads running inside.
Cloud Run Metrics
Track request count, latency, instance count, and CPU/memory utilization for Cloud Run services — including per-revision breakdowns.
BigQuery Cost & Performance
Query slot usage, bytes billed, job duration, and error rates correlated with cost attribution per project, dataset, and user.
Pub/Sub Queue Depth
Monitor subscription message backlogs, oldest unacked message age, and publish rate to detect downstream consumer issues before they cascade.
Multi-Project Consolidated View
Aggregate metrics across all your GCP projects into a single workspace with per-project filtering and cross-project alert correlation.
Cloud SQL & Spanner
Database connection counts, query latency, replication lag, and storage utilization for Cloud SQL (MySQL/PostgreSQL) and Spanner.
gcloud Setup Script
Run these commands to create the service account and assign the required roles.
#!/bin/bash
# TigerOps GCP Integration Setup
# Replace PROJECT_ID with your GCP project ID
PROJECT_ID="your-project-id"
SA_NAME="tigerops-monitoring"
SA_EMAIL="${SA_NAME}@${PROJECT_ID}.iam.gserviceaccount.com"
# Create service account
gcloud iam service-accounts create $SA_NAME \
--display-name="TigerOps Monitoring" \
--project=$PROJECT_ID
# Assign read-only monitoring roles
gcloud projects add-iam-policy-binding $PROJECT_ID \
--member="serviceAccount:${SA_EMAIL}" \
--role="roles/monitoring.viewer"
gcloud projects add-iam-policy-binding $PROJECT_ID \
--member="serviceAccount:${SA_EMAIL}" \
--role="roles/cloudasset.viewer"
gcloud projects add-iam-policy-binding $PROJECT_ID \
--member="serviceAccount:${SA_EMAIL}" \
--role="roles/container.viewer"
# Download JSON key (or configure Workload Identity instead)
gcloud iam service-accounts keys create tigerops-key.json \
--iam-account="${SA_EMAIL}" \
--project=$PROJECT_ID
echo "Upload tigerops-key.json to the TigerOps GCP integration panel."
echo "Service Account: ${SA_EMAIL}"Common Questions
What GCP permissions does TigerOps require?
TigerOps requires the Monitoring Viewer and Cloud Asset Viewer IAM roles. For GKE workload metrics, the Kubernetes Engine Viewer role is also needed. No write permissions are ever requested. We provide a gcloud setup script in our documentation.
Does TigerOps support Workload Identity Federation for GCP?
Yes. Instead of a JSON service account key, you can configure Workload Identity Federation for keyless authentication. This is the recommended approach for production environments as it eliminates long-lived credentials.
Can TigerOps monitor multiple GCP projects from one workspace?
Yes. You can connect any number of GCP projects to a single TigerOps workspace. Metrics from all projects are unified in dashboards and you can filter by project, region, or service at any time.
How does TigerOps complement Google Cloud Monitoring?
Google Cloud Monitoring is excellent for GCP-native metrics but lacks cross-cloud correlation and AI-powered root cause analysis. TigerOps ingests Cloud Monitoring data alongside your application traces, logs from other clouds, and custom business metrics — giving the AI SRE a complete picture to reason over.
Is GKE monitoring agentless?
For GKE system metrics (node CPU, memory, pod restarts), TigerOps can pull data from the Cloud Monitoring API agentlessly. For workload-level application metrics and traces, deploying the TigerOps DaemonSet or using the OpenTelemetry collector is recommended.
Connect Google Cloud in Minutes
No credit card required. Read-only permissions. SOC 2 Type II compliant.