Skip to main content
Connecting GCP to NOFire AI lets NOFire query Cloud Logging, Cloud Monitoring, and Cloud Trace during root-cause analysis. NOFire queries GCP data alongside your Kubernetes graph from Edge, so signals from GCP-managed infrastructure are correlated with your cluster state. To connect, you’ll create a GCP Service Account with read-only access to the logging, monitoring, and trace APIs.

​
Step 1: Create a Service Account

Create a service account in GCP

  1. Open the GCP IAM console for the project you want to connect.
  2. Click Create service account.
  3. Name it nofire and click Create and continue.
  4. Assign the following roles:
    • Logs Viewer (roles/logging.viewer) — read access to Cloud Logging
    • Monitoring Viewer (roles/monitoring.viewer) — read access to Cloud Monitoring metrics
    • Cloud Trace User (roles/cloudtrace.user) — read access to Cloud Trace
  5. Click Done to create the account.
These are read-only roles. NOFire does not write to or modify any GCP resources.

Download credentials JSON

  1. Open the service account you just created.
  2. Go to the Keys tab and click Add key → Create new key.
  3. Select JSON and click Create. A credentials file downloads automatically.
  4. Keep this file secure — you’ll upload it to NOFire in Step 2.

​
Step 2: Add GCP Connection to NOFire AI

Navigate to the Connections tab

​
What NOFire queries

During root-cause analysis, NOFire queries GCP for: GCP signals are evaluated alongside Kubernetes graph data from Edge and any other connected observability backends.

​
Multiple projects

To connect additional GCP projects, add a separate connection for each one. Each connection requires its own service account and credentials JSON.