Google Cloud Platform is Google's suite of cloud computing services, offering infrastructure, data analytics, machine learning, and developer tools across a global network of regions and availability zones.
Resolve AI connects to your Google Cloud environment to ingest logs from Google Cloud Observability, correlating them against infrastructure state, code changes, and signals from your other integrated tools to surface root cause during investigations.

Distributed failures in Google Cloud rarely surface where they originate. Resolve AI ingests logs from Google Cloud Observability and correlates them against infrastructure state, deployment history, and signals from your other integrated tools to trace failures back to their source.
Resolve AI queries log containers across configured projects and organizations to surface error patterns and trace failures through GCP services.
A single integration spans projects, folders, or entire organizations, so failures that cross GCP project boundaries don't require separate queries.
Resolve AI correlates log signals against deployment history to connect service errors and GKE failures to the change that preceded them.
Choose between a Service Account Key for quick setup or Workload Identity Federation to avoid storing long-lived static credentials.
Resolve AI connects GCP logs to Kubernetes state, code changes, and stack alerts so investigations span the full environment, not just the cloud layer.
Resolve AI connects with the minimum permissions needed to investigate, reason, and act across your Google Cloud environment. Log queries are scoped to the projects, folders, or organizations you configure during setup, so Resolve AI only reads data within those boundaries.
Resolve AI requires only roles/logging.viewer on your GCP project. No write access is granted, and raw log data is never retained outside of active investigations.
Everything Resolve AI ingests or queries from your Google Cloud environment, with step-by-step docs in the setup guide.
Queries log containers across projects, folders, and organizations to surface error patterns and trace failures through GCP services.
A single integration covers multiple resource scopes as projects, folders, or entire organizations, without additional configuration.
Connects using a GCP service account private key JSON. The simplest path to get started.
Authenticates to GCP using Resolve AI's AWS identity, so no long-lived private key is stored. Recommended for stricter security postures.
Log queries are restricted to the projects, folders, or organizations you configure as resource names; nothing outside those scopes is readable.
Google Cloud Platform is Google's suite of cloud computing services, offering infrastructure, data analytics, machine learning, and developer tools across a global network of regions and availability zones.
Resolve AI requires a service account with roles/logging.viewer assigned on your GCP project. No write permissions are required. Full setup instructions for both authentication methods are in the setup guide.
It depends on the authentication method. With Service Account Key, the private key JSON is stored securely within your Resolve AI integration configuration. With Workload Identity Federation, no long-lived private key is stored, authentication uses Resolve AI's AWS identity and temporary federated credentials.
Yes. A single integration supports multiple resource scopes. Add as many projects/PROJECT_ID, folders/FOLDER_ID, or organizations/ORG_ID entries as needed during setup.
Service Account Key is the simpler option for most teams, while Workload Identity Federation is recommended when your security policy discourages storing static long-lived credentials.
Resolve AI queries logs from any GCP service that writes to Cloud Logging, including GKE, Cloud Run, Cloud Functions, Compute Engine, and others. Coverage depends on which log containers are configured in your integration.