Skip to main content
Use OpenTelemetry to collect telemetry from your Google Cloud Platform workloads including Cloud Run, Cloud Functions, App Engine, Compute Engine, and other GCP services. This data answers questions like:
  • Which Cloud Run services are experiencing the highest latency?
  • How are my Cloud Functions performing across different regions?
  • What is the error rate for my Pub/Sub topics?
  • Are there any performance bottlenecks in my Cloud SQL or Firestore operations?
Adding telemetry to GCP and then analyzing with Honeycomb provides a flexible way to aggregate, structure, and enrich events from applications running on Google Cloud Platform. This data answers questions like:
  • How did response time change after scaling up my Cloud Run services?
  • How does application performance vary across GCP regions?
  • Are application errors happening in specific services, or across the entire environment?

​
Getting Started

Honeycomb supports GCP through OpenTelemetry Collectors that can collect telemetry from your Google Cloud Platform workloads. This setup allows you to send telemetry from Cloud Run, Cloud Functions, App Engine, Compute Engine, and other GCP services to Honeycomb.

​
Before You Begin

Before you begin, you should have:
  • A GCP project with the services you want to monitor
  • Appropriate IAM permissions to configure monitoring
  • A Honeycomb Ingest API Key You’ll need a Honeycomb Ingest API Key with the Can create services/datasets permission. This key lets your application send telemetry to Honeycomb and create a dataset for your service.
    When deploying to production, replace this key with a separate key that does not allow dataset creation. This helps protect your data structure in live environments.

​
Getting Help

To ask questions and learn more, join our Pollinators Community Slack.