GCP Monitoring

Manage Cloud Monitoring alerting — alert policies, notification channels, and snoozes

The GCP Monitoring integration lets your agents manage Cloud Monitoring alerting — list and edit alerting policies, manage notification channels, and create snoozes to silence alerts for a time window — against a specific Google Cloud project. Pair it with GCP Logging for read access to logs and logs-based metrics.

Prerequisites

A Google Cloud project with Cloud Monitoring enabled.
A Project ID from the Google Cloud Console.
Credentials, by one of three methods:
- Google OAuth — connect a Google account and grant the Monitoring scope (full monitoring for create/update/delete, or monitoring.read for read-only).
- Workload Identity Federation — paste an external_account credential-configuration JSON (no key stored). Generate it with gcloud iam workload-identity-pools create-cred-config.
- Service account key — paste a service-account JSON key created under IAM & Admin → Service Accounts → Keys, granted the Monitoring Editor role (or Monitoring Viewer for read-only).

Unlike GCP Logging, GCP Monitoring does not offer the "Grant Fruxon Service Account Access" shared-credential path — use OAuth, Workload Identity Federation, or a service-account key.

Setup

Open Integrations from the sidebar
Select GCP Monitoring from the catalog
Click Add Integration Config
Give the config a display name (e.g., "GCP Monitoring — Prod project").
Enter the Project ID.
Pick the auth method: connect a Google account, paste a Workload Identity credential configuration, or paste a service-account key.
Save the config

Using in Your Agent

Open your agent in Agent Studio and select an Agent Step
Under Attached Integration Configurations, click Attach configuration and choose your config
Attach GCP Monitoring tools from the tools panel
Tools are referenced as gcp_monitoring.list_alert_policies, gcp_monitoring.create_snooze, etc.

The create/update tools take a full Cloud Monitoring v3 JSON body (e.g. an AlertPolicy or NotificationChannel), so the agent should be prompted with the resource shape or given an example.

Available Tools

Alert policies

Tool	Description	Action Type
`list_alert_policies`	List alerting policies in the project (supports a Monitoring filter expression)	ReadOnly
`get_alert_policy`	Get a single alerting policy by full resource name	ReadOnly
`create_alert_policy`	Create a new alerting policy from an AlertPolicy JSON body	Reversible
`update_alert_policy`	Update an existing alerting policy (update mask + JSON body)	Reversible
`delete_alert_policy`	Delete an alerting policy by full resource name	Irreversible

Notification channels

Tool	Description	Action Type
`list_notification_channels`	List notification channels (email, SMS, Slack, PagerDuty, webhooks, …)	ReadOnly
`get_notification_channel`	Get a single notification channel by full resource name	ReadOnly
`list_notification_channel_descriptors`	List available channel types and their required fields	ReadOnly
`create_notification_channel`	Create a notification channel from a JSON body	Reversible
`update_notification_channel`	Update an existing notification channel (update mask + JSON body)	Reversible
`delete_notification_channel`	Delete a notification channel (optional `force`)	Irreversible

Snoozes

Tool	Description	Action Type
`list_snoozes`	List snoozes in the project	ReadOnly
`get_snooze`	Get a single snooze by full resource name	ReadOnly
`create_snooze`	Create a snooze to silence alerts over a time interval	Reversible
`update_snooze`	Update a snooze — e.g. extend it or end it early	Reversible