GCP

Connect GCP to NOFire AI so NOFire can query Cloud Logging, Cloud Monitoring, and Cloud Trace during root-cause analysis. NOFire queries GCP data alongside your Kubernetes graph from Edge, so NOFire correlates signals from GCP-managed infrastructure with your cluster state. To connect, you will create a GCP Service Account with read-only access to the logging, monitoring, and trace APIs.

​

Prerequisites

• A Google Cloud project, and permission to create service accounts and keys in it.
• The project ID, and the regions you want discovered.

​

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 will upload it to NOFire in Step 2.

​

Step 2: Add GCP connection to NOFire AI

Navigate to the Connections tab

1. In the NOFire AI dashboard, go to Connections and click Connect on Google Cloud Platform.
2. Enter your connection details:
   • Connection Name: a descriptive label (for example, production-gcp)
   • Project ID: the GCP project ID you want NOFire to query
   • Regions: select at least one GCP region
   • Service Account JSON: paste the contents of the JSON key file from Step 1. If you leave Project ID empty first, a valid key fills it in.
3. Click Save . NOFire AI tests the connection as it saves.

Once saved, NOFire begins querying Cloud Logging, Cloud Monitoring, and Cloud Trace during root-cause analysis for workloads in the connected project.

​

What NOFire queries

During root-cause analysis, NOFire queries GCP for: NOFire evaluates GCP signals alongside Kubernetes graph data from Edge and 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.

​

Test the connection

1. Open the Connections dashboard and make sure that the GCP connection status is READY. A connection that stays in an error state did not authenticate.
2. Ask NOFire a question that needs GCP context, for example “which GCP resources back the checkout service?”. An answer that names your resources confirms the connection works end to end.

​

Troubleshooting