Choose which Google Cloud resources are monitored
Discover the virtual machines, databases, apps and functions in your Google Cloud projects and choose what is monitored, where it goes in Infrastructure and how often its metrics are read.
On this page
Once the Google Cloud connection is created, on the same tab you choose which resources in your projects ARGUNIS monitors. It works the same as with AWS, Azure and Railway: anything you don't choose is not monitored and does not count toward the plan.
ARGUNIS only reads Google Cloud: it never starts, stops or changes anything in your projects.
Before you start
A Google Cloud connection. See Connect AWS, Google Cloud, Azure, Cloudflare or Coolify.
Give the connection's service account these roles on each project you want to monitor:
roles/compute.viewer,roles/cloudsql.viewer,roles/run.viewer,roles/cloudfunctions.viewerandroles/monitoring.viewer(orroles/viewer, which includes them). In What this connection enables, Monitoring row, the Copy commands button gives you thegcloudcommands. You can also do it in the console: IAM & Admin → IAM → Grant access.Choosing what is monitored is up to operators and administrators.
What is monitored for each resource
Resource | Goes in | Status | Metrics |
|---|---|---|---|
Virtual machine (Compute Engine) | Servers | Running, stopped or suspended | CPU and network |
Database (Cloud SQL) | Databases | Available, stopped or failed | CPU, memory, used disk and connections |
App (Cloud Run) | Servers | Ready or failed | Requests, 5xx errors and p95 latency |
Function (Cloud Functions) | Other hosts | Active or failed | Executions, errors and p95 duration |
The place is a suggestion: you can choose another one.
Choose the resources
Go to Settings → Monitoring → Cloud services and open the Google Cloud tab.
In Google Cloud resources, if you have more than one connection, choose which one (you can also choose it in the Connection column of the Monitoring row, in What this connection enables).
In Projects, leave the field empty to query the projects the connection can see (up to 10) or enter the project IDs separated by commas. Click Query.
The resources appear grouped by project. In each row:
Check Monitor.
Choose the Place in Infrastructure and the Inventory group.
Choose the Interval: every 1, 5 or 15 minutes.
Click Save selection.
Google Cloud does not charge for reading metrics within the Cloud Monitoring quota.
Virtual machines and databases count as servers in your plan; apps and functions, as services. If the plan is not enough, the selection is not saved and you are notified.
If an API is not enabled in a project, or the service account is missing a role, a notice says so above the results.
Stop monitoring
Uncheck the resource and click Save selection. Its history is deleted.
If a monitored resource no longer shows up in Google Cloud, a notice says so, with the Stop monitoring them button.
While the connection is monitoring resources, it cannot be removed.
What happens next
Each resource appears in Infrastructure, in its place, in the Cloud resources section. See View cloud services.
A stopped or failed resource opens a critical incident. CPU, storage or errors above the threshold open a notification. Both close on their own when things return to normal.