Google Pub/Sub Integration
Topic throughput, subscription backlog, and acknowledgment latency monitoring for GCP Pub/Sub. Detect backlog growth early and correlate message delivery failures with consuming services.
How It Works
Create a GCP Service Account
Create a service account with the Monitoring Viewer and Pub/Sub Viewer roles. This allows TigerOps to collect topic and subscription metrics without publishing or consuming messages.
Enable Cloud Monitoring API
Enable the Cloud Monitoring API and Pub/Sub API in your GCP project. TigerOps uses these to collect publish rates, subscription backlog depths, and acknowledgment latency.
Configure TigerOps Pub/Sub
Enter your project credentials in TigerOps and select the topics and subscriptions to monitor. TigerOps auto-discovers all Pub/Sub resources in your project.
Set Backlog and Latency Alerts
Define subscription backlog thresholds, acknowledgment latency SLOs, and publish rate anomaly detection. TigerOps predicts backlog growth and fires alerts before consumers fall behind.
What You Get Out of the Box
Topic Throughput Monitoring
Track publish message rates, byte rates, and undelivered message counts per topic. TigerOps detects publish rate anomalies and correlates them with upstream producer service metrics.
Subscription Backlog Tracking
Monitor subscription backlog message counts and oldest unacked message age. TigerOps predicts when backlog growth will breach your SLO and fires early alerts with estimated time to threshold.
Acknowledgment Latency
Track per-subscription acknowledgment latency percentiles (P50, P95, P99). TigerOps correlates ack latency increases with consumer CPU saturation, code deployments, and downstream failures.
Dead Letter Topic Monitoring
Monitor dead letter topic message rates to detect processing failures. TigerOps alerts when dead letter queues fill up and traces failures back to the originating subscription and message payload patterns.
Push vs Pull Subscription Metrics
Differentiate between push and pull subscription performance. For push subscriptions, TigerOps monitors endpoint delivery success rates, HTTP response codes, and retry counts.
Cross-Service Message Flow
TigerOps maps Pub/Sub message flows across your architecture. When a publishing service produces a spike, TigerOps automatically links it to the consuming service and any downstream effects on your stack.
Pub/Sub Integration Config
Configure TigerOps to monitor your GCP Pub/Sub topics and subscriptions.
# TigerOps GCP Pub/Sub Integration
# Required IAM roles:
# roles/monitoring.viewer
# roles/pubsub.viewer
integrations:
gcp_pubsub:
project_id: "your-gcp-project-id"
credentials_file: "./tigerops-sa-key.json"
# Topics to monitor (empty = all topics)
topics:
- orders-created
- payment-events
- user-activity
# Subscriptions to monitor (empty = all subscriptions)
subscriptions:
- orders-processor-sub
- analytics-pipeline-sub
- notification-service-sub
scrape_interval: 60s
metrics:
- pubsub.googleapis.com/topic/send_message_operation_count
- pubsub.googleapis.com/subscription/num_undelivered_messages
- pubsub.googleapis.com/subscription/oldest_unacked_message_age
- pubsub.googleapis.com/subscription/num_outstanding_messages
alerts:
backlog_message_count: 10000
oldest_unacked_message_age_seconds: 300
dead_letter_rate_per_minute: 10
ack_latency_p99_seconds: 30Common Questions
How is this GCP Pub/Sub page different from the general Google Pub/Sub integration?
This page focuses on GCP-native Pub/Sub monitoring via the Cloud Monitoring API and GCP service account authentication. It covers GCP-specific features like dead letter topics, Cloud Functions triggers, and multi-project Pub/Sub topologies within GCP.
Can TigerOps alert when subscription backlog grows faster than consumers can process?
Yes. TigerOps computes the backlog growth rate and compares it to your consumer throughput to predict when the backlog will breach your configured threshold. You receive an alert with estimated time to breach and the growth rate trend.
Does TigerOps monitor Pub/Sub Lite as well as standard Pub/Sub?
Yes. TigerOps supports both standard Pub/Sub and Pub/Sub Lite. Pub/Sub Lite metrics include partition-level throughput, storage utilization, and quota usage, displayed separately from standard Pub/Sub subscriptions.
How are push subscription delivery failures tracked?
TigerOps monitors the delivery attempt count and delivery error counts for push subscriptions via the Cloud Monitoring API. When push endpoint error rates spike, TigerOps correlates the failure with the endpoint service health metrics if it is also monitored.
Can TigerOps monitor Pub/Sub topics across multiple GCP projects?
Yes. Add a service account for each GCP project or use cross-project IAM bindings. TigerOps displays Pub/Sub metrics from all projects in a unified dashboard and can correlate cross-project message flows.
Catch Pub/Sub Backlog Growth Before Consumers Fall Behind
Predictive backlog alerts, dead letter monitoring, and AI cross-service message flow correlation. Connect in minutes.