Google Cloud Functions Integration
Serverless function execution metrics, cold starts, and error tracking on GCP. Monitor invocation latency, error rates, and memory utilization across all your functions.
How It Works
Create a GCP Service Account
Create a service account with the Monitoring Viewer and Cloud Functions Viewer roles. Download the JSON key to authenticate TigerOps with Cloud Monitoring.
Enable Cloud Monitoring API
Enable the Cloud Monitoring API and Cloud Functions API in your GCP project. TigerOps will pull invocation counts, execution times, and error rates automatically.
Configure TigerOps Integration
Enter your project ID and credentials in TigerOps. Select the functions and regions to monitor. TigerOps discovers all deployed functions and begins collecting metrics.
Set Error and Latency Alerts
Configure error rate thresholds, execution timeout alerts, and cold start frequency limits. TigerOps fires predictive alerts before error budgets are exhausted.
What You Get Out of the Box
Invocation & Execution Metrics
Track invocation counts, execution times (P50, P95, P99), memory utilization, and network egress per function. Compare performance across function versions and deployments.
Cold Start Monitoring
Measure cold start frequency and duration per function. TigerOps identifies functions with excessive cold starts and recommends minimum instance configuration or memory adjustments.
Error Rate Tracking
Monitor function error rates, crash loops, and timeout events. TigerOps correlates error spikes with new deployments, dependency changes, and upstream trigger failures.
Trigger Source Visibility
Track metrics by trigger type — HTTP, Pub/Sub, Cloud Storage, Firestore, and Eventarc. Understand which event sources are driving invocation volume and error rates.
Concurrency & Throttling
Monitor active instance counts, throttled invocation rates, and concurrency limits. TigerOps alerts when functions approach their concurrency ceiling and identifies traffic burst patterns.
Cost & Memory Optimization
TigerOps tracks GBs-seconds consumed per function and correlates memory allocation with actual usage. Identify over-provisioned functions and reduce costs with data-driven memory recommendations.
Cloud Functions Integration Config
Configure TigerOps to monitor your Cloud Functions with service account credentials.
# TigerOps Cloud Functions Integration
# Required IAM roles:
# roles/monitoring.viewer
# roles/cloudfunctions.viewer
integrations:
gcp_cloud_functions:
project_id: "your-gcp-project-id"
credentials_file: "./tigerops-sa-key.json"
regions:
- us-central1
- us-east1
- europe-west1
# Functions to monitor (empty = all functions)
functions:
- payment-webhook-handler
- image-thumbnail-generator
- user-notification-sender
scrape_interval: 60s
metrics:
- cloudfunctions.googleapis.com/function/execution_count
- cloudfunctions.googleapis.com/function/execution_times
- cloudfunctions.googleapis.com/function/user_memory_bytes
- cloudfunctions.googleapis.com/function/active_instances
- cloudfunctions.googleapis.com/function/network_egress
alerts:
error_rate_percent: 1.0
execution_time_p99_ms: 5000
cold_start_rate_percent: 10
memory_utilization_percent: 85
timeout_count_per_minute: 5Common Questions
Does TigerOps support both Cloud Functions 1st gen and 2nd gen?
Yes. TigerOps monitors both 1st and 2nd generation Cloud Functions. For 2nd gen functions (built on Cloud Run), TigerOps collects both the Cloud Functions metrics and the underlying Cloud Run instance metrics for complete observability.
How does TigerOps detect cold starts for Cloud Functions?
TigerOps uses the cloudfunctions.googleapis.com/function/execution_count metric combined with instance count change signals to identify cold start events. Cold start duration is approximated from the first-execution latency spike pattern.
Can TigerOps alert on function execution timeouts?
Yes. TigerOps monitors the execution time distribution and fires alerts when a function approaches its configured timeout limit (default 60s for HTTP, up to 540s for background). You can also alert on timeout error events directly.
How are Cloud Functions correlated with Pub/Sub triggers in TigerOps?
TigerOps automatically correlates Cloud Functions invocation metrics with the Pub/Sub topic subscription metrics that trigger them. When a Pub/Sub backlog grows and function invocations spike, TigerOps links both signals in a single incident view.
Can I monitor Cloud Functions deployed in different GCP projects?
Yes. Add a service account for each GCP project or use cross-project IAM bindings. TigerOps displays all monitored projects in a unified dashboard with project-level filtering and aggregation.
Gain Full Visibility Into Your Serverless Functions
Cold start tracking, error rate alerts, and AI-powered root cause analysis for Cloud Functions. Deploy in minutes.