Monitor Google Cloud Platform instances and resources in real time. Track availability, CPU, memory, disk, and network performance across your GCP infrastructure from a single view.
Cloudmon supports agentless monitoring of GCP resources using Google Cloud's native APIs. Once a GCP account is added, Cloudmon automatically discovers your Compute Engine instances and begins collecting performance and availability metrics at the configured discovery interval.
Navigate to Cloud → GCP to view all monitored GCP accounts and their associated resources.
Cloudmon connects to your GCP project using a Service Account with read-only permissions. It calls the Compute Engine and Cloud Monitoring APIs at regular intervals to pull metrics, resource lists, and configuration data. Nothing is installed inside your GCP environment. The connection is made from a Cloudmon probe using the Service Account key you upload, so the probe requires outbound internet access to reach the GCP APIs.
Cloudmon connects to GCP using a Service Account JSON file with the appropriate read-only permissions. Before adding a GCP account in Cloudmon, complete the following steps in the Google Cloud Console:
To start monitoring GCP in Cloudmon, navigate to Cloud → GCP → Add Google Cloud. The form is split into three sections.
Configure the monitor name, services to monitor, and discovery settings.
| Field | Description |
| Probe* | The Cloudmon probe that connects to the GCP account and collects the data. The probe requires outbound internet access to reach the GCP APIs. |
| Monitor Name | A display name for this GCP account in Cloudmon, for example Production GCP Account. |
| Enable Auto-Discovery | When enabled, Cloudmon automatically discovers new resources added to the GCP project at each discovery interval. Enabled by default. |
| Services | Select the GCP services to monitor. Currently supports Compute Instance. |
| Discovery Interval | How frequently Cloudmon scans the GCP project for new or removed resources. Options: 6 hours, 12 hours, Daily, Weekly. |
Upload the JSON key file generated for the GCP Service Account. Click Choose File and select the downloaded JSON key file from your machine. Cloudmon uses this file to authenticate all API requests to your GCP project.
Configure how Cloudmon handles resource changes and filter which resources are monitored using GCP labels.
| Option | Description |
| Mute Resource Deletion Alerts | When enabled, Cloudmon will not raise an alert when a monitored GCP resource is removed. Useful for auto-scaling environments where instances are regularly terminated. |
| Continue Monitoring Terminated Resources | When enabled, Cloudmon continues tracking a resource after it has been terminated in GCP, retaining its historical data in the Cloudmon database. |
| Enable Auto Delete | When enabled, Cloudmon automatically removes a monitor from its database when the corresponding GCP resource is deleted. |
| Exclude / Include Resources Using Labels | Filter which GCP resources Cloudmon monitors based on GCP labels. Select Exclude to skip resources with specific labels, or Include to monitor only resources with specific labels. |
Optionally configure grouping and dependency settings for this GCP account.
| Field | Description |
| Depends On | Link this GCP account to a parent monitor. Alerts for this account are suppressed if the parent monitor is down. |
| Groups | Assign this GCP account to one or more Cloudmon groups for organised access and bulk alarm rule association. |
| Tags | Optional labels for organising and filtering this GCP account within Cloudmon. |
Once all fields are filled in, click Save to add the account. Cloudmon will initiate the first discovery cycle immediately.