Skip to main content
What you’ll get: ewake can query your GCP Cloud Logging logs in real time, correlating log entries with alerts, deployments, and infrastructure events across your Google Cloud projects.

​
Prerequisites

  • A Google Cloud project with logs flowing into Cloud Logging
  • Owner or IAM Admin access to create a service account and assign roles
  • Access to your ewake dashboard

​
Configuration

1

Create a Service Account

In the GCP Console, go to IAM & Admin → Service Accounts → click Create Service Account.Give it a name (e.g. ewake-logs) and click Create and continue.
2

Grant the logging.viewer role

In the Grant this service account access to project step, assign the role:Click Continue, then Done.
Logs Viewer is read-only. Ewake cannot write, delete, or modify any log entries or logging configuration.
3

Generate a JSON key

Open the service account you just created → go to the Keys tab → click Add Key → Create new key → select JSON → click Create.A .json file will be downloaded to your machine. Keep it safe, it contains the credentials ewake will use.
If you lose this key, you can revoke it and generate a new one from the same Keys tab. Never commit the JSON file to source control.
4

Connect in ewake

In your ewake dashboard, go to Integrations → GCP Cloud Logging → click Connect with API key.Fill in the following fields:
5

Save

Click Save.
GCP Cloud Logging is connected. Ewake can now query your logs during investigations.

​
Connect more than one project

GCP Cloud Logging is a multi-instance integration: connect as many projects as you need, one at a time. Give each connection an Instance name that tells them apart, for example prod, staging. Letters, digits, - or _, starting with a letter or digit, max 64 characters. Each connection carries its own GCP project ID and service account key, so one service account never needs access across projects. They’re listed under Connected projects in the integration dialog, where you can add another with Connect with API key or remove one on its own.
Ewake only requires read access to GCP Cloud Logging. It never writes logs, modifies sinks, or changes any IAM policies in your project.