Email

To add an email notification channel, do the following:

1. In the Google Cloud console, go to thenotifications Alerting page:

   Go toAlerting

   If you use the search bar to find this page, then select the result whose subheading isMonitoring.

2. In the toolbar of the Google Cloud console,select your Google Cloud project. ForApp Hubconfigurations, select the App Hub host project or management project.
3. ClickEdit notification channels.
4. In theEmail section, clickAdd new.
5. Enter a single email address and a description.
6. ClickSave.

If you use a group email address as the notification channel for an alerting policy, then configure the group to accept mail fromalerting-noreply@google.com.

You can create email channels during the creation of an alerting policy. For more information, seeCreate a channel on demand.

Mobile App

Use theGoogle Cloud console Mobile App to monitor your Google Cloud console resources and Monitoring information from anywhere. Google Cloud console Mobile App notifications are either sent to a specific device or to a specific user:

• Device indicates that notifications are sent only to the specific device that created the notification channel. For device-scoped notification channels, theDisplay name field includes device information.
• User indicates that the notifications are sent to all of your devices that have the Google Cloud console Mobile App installed.

Cloud Monitoring determines the notification scope when the channel is created. You can't select or change the scope.

To configure a Google Cloud console Mobile App notification channel for a specific Google Cloud project, do the following:

1. Install the Google Cloud console Mobile App from your mobile device's app store.

2. Select a project for viewing in the Google Cloud console Mobile App.

   After you select a project, a data exchange between the app and the selected Google Cloud project occurs. A notification channel is created when one doesn't exist, and after a few minutes, this channel is listed under theMobile Devices section of theNotification channels page.

To add your mobile device as a notification channel for an alerting policy, in the alertingNotifications section, selectGoogle Cloud console (mobile) and then choose your mobile device from the list.

PagerDuty

PagerDuty supports two-way synchronization with Monitoring. As a result, the following are true:

• If an incident is created in Monitoring, then an incident is opened in PagerDuty.
• You can't use PagerDuty to close an incident in Monitoring.
• If you resolve an incident in PagerDuty and if Monitoring has the incident open, then the incident is reopened in PagerDuty.

To set up PagerDuty notifications, do the following:

1. In yourPagerDuty account, configure the integration in a new service or add the integration to an existing service.
   1. Create an account or sign in to an existing account.
   2. Go to theServices page.
   • To create a service, do the following:
     1. Click+ New Service.
     2. Enter a service name and description, and then clickNext.
     3. Configure an escalation policy, and then clickNext.
     4. If your PagerDuty account supports incident grouping and transient alerts, configure them, and then clickNext.
     5. On the integrations setup page, in theSearch for an integration(s) toolbar, enterEvents API v1, and then clickCreate Service. You are then returned to theIntegrations panel of your new service.
   • To edit an existing service, do the following:
     1. Select a service from your Service Directory.
     2. On your service page, select theIntegrations panel.
     3. Click+ Add another integration to go to the integrations setup page.
     4. On the integrations setup page, in theSearch for an integration(s) toolbar, enterEvents API v1, and then clickAdd. You are then returned to theIntegrations panel of your edited service.
   3. On your service'sIntegrations panel, find the listing for your new integration, expand its menu, and then copy the integration key.
   4. Optional:Configure PagerDuty to accurately map incident severity values from Monitoring.
2. In Cloud Monitoring, add the PagerDuty notification channel:

   1. In the Google Cloud console, go to thenotifications Alerting page:

      Go toAlerting

      If you use the search bar to find this page, then select the result whose subheading isMonitoring.

   2. In the toolbar of the Google Cloud console,select your Google Cloud project. ForApp Hubconfigurations, select the App Hub host project or management project.
   3. ClickEdit notification channels.
   4. In thePagerDuty section, clickAdd new.
   5. Enter theDisplay Name. This name should match the name of the PagerDuty service where you configured your new integration in Step 1.
   6. Paste the integration key that you copied in Step 1 into theService Key field.
   7. ClickSave.

When you create an alerting policy, selectPagerDuty in theNotifications section and choose your PagerDuty configuration.

The JSON packet for PagerDuty has the following format:

{"description":Astringofvariousfieldsintheincident,"details":JSONpayloadwithschemaversion1.2.}

To view an example and the schema for thedetails field, expand the following sections.

{  "incident": {    "incident_id": "0.opqiw61fsv7p",    "renotify": true,    "scoping_project_id": "internal-project",    "scoping_project_number": 12345,    "url": "https://console.cloud.google.com/monitoring/alerting/incidents/0.lxfiw61fsv7p?project=internal-project",    "severity": "no severity",    "started_at": 1577840461,    "ended_at": 1577877071,    "state": "closed",    "resource_id": "11223344",    "resource_name": "internal-project gke-cluster-1-default-pool-e2df4cbd-dgp3",    "resource_display_name": "gke-cluster-1-default-pool-e2df4cbd-dgp3",    "resource_type_display_name": "VM Instance",    "resource": {      "type": "gce_instance",      "labels": {        "instance_id": "11223344",        "project_id": "internal-project",        "zone": "us-central1-c"      }    },    "metric": {      "type": "compute.googleapis.com/instance/cpu/utilization",      "displayName": "CPU utilization",      "labels": {        "instance_name": "the name of the VM instance"      }    },    "metadata": {      "system_labels": { "labelkey": "labelvalue" },      "user_labels": { "labelkey": "labelvalue" }    },    "policy_name": "Monitor-Project-Cluster",    "policy_user_labels" : {        "user-label-1" : "important label",        "user-label-2" : "another label"    },    "condition_name": "VM Instance - CPU utilization [MAX]",    "threshold_value": "0.9",    "observed_value": "0.835",    "condition": {      "name": "projects/internal-project/alertPolicies/1234567890123456789/conditions/1234567890123456789",      "displayName": "VM Instance - CPU utilization [MAX]",      "conditionThreshold": {        "filter": "metric.type=\"compute.googleapis.com/instance/cpu/utilization\" resource.type=\"gce_instance\" metadata.system_labels.\"state\"=\"ACTIVE\"",        "aggregations": [          {            "alignmentPeriod": "120s",            "perSeriesAligner": "ALIGN_MEAN"          }        ],        "comparison": "COMPARISON_GT",        "thresholdValue": 0.9,        "duration": "0s",        "trigger": {          "count": 1        }      }    },    "documentation": {      "content": "TEST ALERT\n\npolicy.name=projects/internal-project/alertPolicies/1234567890123456789\n\npolicy.display_name=Monitored-Project-NO-GROUPBY\n\ncondition.name=projects/nternal-project/alertPolicies/1234567890123456789/conditions/1234567890123456789\n\ncondition.display_name=VM Instance - CPU utilization [MAX]\n\nproject=internal-project\n\nresrouce.project=internal-project \n\nDONE\n",      "mime_type": "text/markdown",      "subject": "ALERT - No severity",      "links": [        {          "displayName": "Playbook",          "url": "https://myownpersonaldomain.com/playbook?name=${resource.name}"        }      ]    },    "summary": "CPU utilization for internal-project gke-cluster-1-16-default-pool-e2df4cbd-dgp3 with metric labels {instance_name=gke-cluster-1-default-pool-e2df4cbd-dgp3} and system labels {state=ACTIVE} returned to normal with a value of 0.835."  },  "version": "1.2"}

Deprecation policy

Configure PagerDuty to map severity levels

By default, PagerDuty notifications show all incident severity levels as "critical". You can configure event orchestration rules in PagerDuty so that the PagerDuty alert severity matches the Monitoring incident severity:

1. In your PagerDuty account, go to theServices page.
2. Select the PagerDuty service where you receive Google Cloud notifications.
3. ClickSettings.
4. Go to theEvent Management section and then clickView Orchestration Rules.
5. ClickNew Rule.
6. For each Monitoring severity value that you want to convert, create a conditional rule that maps the severity value to an equivalent PagerDuty value:
   1. In the menu underStep 1: When should this rule be applied?, selectIf events match certain conditions.
   2. Select the code editor.
   3. In theIf section, enterevent.custom_details.incident.severity matches part 'VALUE', whereVALUE is the name of a Monitoring severity value, then clickNext.
   4. UnderStep 2: What action(s) should be applied, selectAlert Data.
   5. Set the alert severity to a value that matches the Monitoring value that you entered in Step C, then save your changes.
7. Optional: To add additional rules, clickElse rule.

SMS

To configure SMS notifications, do the following:

1. In the Google Cloud console, go to thenotifications Alerting page:

   Go toAlerting

   If you use the search bar to find this page, then select the result whose subheading isMonitoring.

2. In the toolbar of the Google Cloud console,select your Google Cloud project. ForApp Hubconfigurations, select the App Hub host project or management project.
3. ClickEdit notification channels.
4. In theSMS section, clickAdd new.

5. Complete the dialog and clickSend Verification Code.

   A verification code is sent to the contact number you provided.

6. Enter the code and clickVerify.

   If you don't receive a code, seeSMS notification messages or verification codes aren't received.

When you set up your alerting policy, select theSMS notification type and choose a verified phone number from the list.

Slack

The Monitoring Slack integration allows your alerting policies to post to a Slack channel when a new incident is created. To set up Slack notifications, do the following:

1. In Slack: Create a Slack workspace and channel at theSlack site. Record the channel URL.

2. In the Google Cloud console, go to thenotifications Alerting page:

   Go toAlerting

   If you use the search bar to find this page, then select the result whose subheading isMonitoring.

3. In the toolbar of the Google Cloud console,select your Google Cloud project. ForApp Hubconfigurations, select the App Hub host project or management project.

4. ClickEdit notification channels.

5. In theSlack section, clickAdd new to open the Slack sign-in page:

   1. Select your Slack workspace.
   2. ClickAllow to enable Cloud Monitoring access to your Slack workspace. This action takes you back to the Monitoring configuration page for your notification channel.
   3. In theSlack Channel Name field, enter the name of the Slack channel you want to use for notifications.
   4. In theCloud Alerting Display Name field, enter a short descriptive statement. Monitoring displays the value of this field on theNotifications channel page.
   5. (Optional) To test the connection between Cloud Monitoring and your Slack workspace, clickSend test notification. If the connection is successful, then you see a messageThis is a test alert notification... in the Slack notification channel that you specified. Check the notification channel to confirm receipt.

6. If the Slack channel you want to use for notifications is a private channel, then you must manually invite the Monitoring app to the channel:

   1. Open Slack.

   2. Go to the channel you specified as your Monitoring notification channel.

   3. Invite the Monitoring app to the channel by entering and sending the following message in the channel:

      /invite @Google Cloud Monitoring

      Be sure you invite the Monitoring app to the privatechannel you specified when creating the notification channel inMonitoring. Inviting the Monitoring appto public channels is optional.

   When you create an alerting policy, selectSlack in theNotifications section and choose your Slack configuration.

Webhooks

Before you configure a Webhook notification channel, consider the following:

• Webhooks only support public endpoints. A public endpoint is fully accessible from the public internet, such as by HTTP (port:80) or HTTPS (port:443). The notification service must be able to establish a connection to the endpoint and, in the case of HTTPS, verify the server's security certificate. If you need notifications sent to an endpoint that isn't public, then create a Pub/Sub notification channel and configure a subscription to the Pub/Sub topic. For more information, seeWebhook notifications fail when configured for a private endpoint.
• If a Cloud Run function is configured as webhook endpoint for a notification channel, then make sure the user invoking the function has the required authentication permission. For more information, seeAuthenticate for invocation andEnabling access to a function.
• To send notification data from Monitoring to Microsoft Teams, you must use an intermediary service such as Power Automate orCloud Run functions. Configure the service to receive the Monitoring webhook notification, convert the data into a Teams-compatible format, and forward the data to the appropriate Microsoft Teams channel.

Configure Webhook notification channels

To configure Webhooks notifications, do the following:

1. The webhook handler: Identify the public endpoint URL to receive webhook data from Monitoring.

2. In the Google Cloud console, go to thenotifications Alerting page:

   Go toAlerting

   If you use the search bar to find this page, then select the result whose subheading isMonitoring.

3. In the toolbar of the Google Cloud console,select your Google Cloud project. ForApp Hubconfigurations, select the App Hub host project or management project.
4. ClickEdit notification channels.
5. In theWebhook section, clickAdd new.
6. Complete the dialog.
7. ClickTest Connection to send a test payload to the Webhook endpoint. You can go to the receiving endpoint to verify delivery.
8. ClickSave.

When you create an alerting policy, selectWebhook in theNotifications section and choose your webhook configuration. The notifications sent by Error Reporting follow the1.0 schema while notifications sent by Monitoring follow the 1.2 schema:

{  "incident": {    "incident_id": "0.opqiw61fsv7p",    "renotify": true,    "scoping_project_id": "internal-project",    "scoping_project_number": 12345,    "url": "https://console.cloud.google.com/monitoring/alerting/incidents/0.lxfiw61fsv7p?project=internal-project",    "severity": "no severity",    "started_at": 1577840461,    "ended_at": 1577877071,    "state": "closed",    "resource_id": "11223344",    "resource_name": "internal-project gke-cluster-1-default-pool-e2df4cbd-dgp3",    "resource_display_name": "gke-cluster-1-default-pool-e2df4cbd-dgp3",    "resource_type_display_name": "VM Instance",    "resource": {      "type": "gce_instance",      "labels": {        "instance_id": "11223344",        "project_id": "internal-project",        "zone": "us-central1-c"      }    },    "metric": {      "type": "compute.googleapis.com/instance/cpu/utilization",      "displayName": "CPU utilization",      "labels": {        "instance_name": "the name of the VM instance"      }    },    "metadata": {      "system_labels": { "labelkey": "labelvalue" },      "user_labels": { "labelkey": "labelvalue" }    },    "policy_name": "Monitor-Project-Cluster",    "policy_user_labels" : {        "user-label-1" : "important label",        "user-label-2" : "another label"    },    "condition_name": "VM Instance - CPU utilization [MAX]",    "threshold_value": "0.9",    "observed_value": "0.835",    "condition": {      "name": "projects/internal-project/alertPolicies/1234567890123456789/conditions/1234567890123456789",      "displayName": "VM Instance - CPU utilization [MAX]",      "conditionThreshold": {        "filter": "metric.type=\"compute.googleapis.com/instance/cpu/utilization\" resource.type=\"gce_instance\" metadata.system_labels.\"state\"=\"ACTIVE\"",        "aggregations": [          {            "alignmentPeriod": "120s",            "perSeriesAligner": "ALIGN_MEAN"          }        ],        "comparison": "COMPARISON_GT",        "thresholdValue": 0.9,        "duration": "0s",        "trigger": {          "count": 1        }      }    },    "documentation": {      "content": "TEST ALERT\n\npolicy.name=projects/internal-project/alertPolicies/1234567890123456789\n\npolicy.display_name=Monitored-Project-NO-GROUPBY\n\ncondition.name=projects/nternal-project/alertPolicies/1234567890123456789/conditions/1234567890123456789\n\ncondition.display_name=VM Instance - CPU utilization [MAX]\n\nproject=internal-project\n\nresrouce.project=internal-project \n\nDONE\n",      "mime_type": "text/markdown",      "subject": "ALERT - No severity",      "links": [        {          "displayName": "Playbook",          "url": "https://myownpersonaldomain.com/playbook?name=${resource.name}"        }      ]    },    "summary": "CPU utilization for internal-project gke-cluster-1-16-default-pool-e2df4cbd-dgp3 with metric labels {instance_name=gke-cluster-1-default-pool-e2df4cbd-dgp3} and system labels {state=ACTIVE} returned to normal with a value of 0.835."  },  "version": "1.2"}

Basic authentication

In addition to the webhook request sent by Cloud Monitoring, basic authentication utilizes the HTTP specification for the username and password. Cloud Monitoring requires your server to return a 401 response with the properWWW-Authenticate header. For more information about basic authentication, see the following:

• RFC Specification
• Basic authentication

Token authentication

Token Authentication requires a query string parameter in the endpoint URL and a key that the server expects to be secret between itself and Monitoring. The following is a sample URL that includes a token:

https://www.myserver.com/stackdriver-hook?auth_token=1234-abcd

If Monitoring posts an incident to the endpoint URL, your server can validate the attached token. This method of authentication is most effective when used with SSL/TLS to encrypt the HTTP request preventing snoopers from learning the token.

For an example server in Python, see thissample server.

Deprecation policy

Pub/Sub

This section describes how to configure Pub/Sub notification channels. For redundancy, we recommend that you create multiple notification channels. Pairing Pub/Sub with Google Cloud console Mobile App, PagerDuty, Webhooks, or Slack is recommended, because Pub/Sub uses a different delivery mechanism.

To configure a Pub/Sub notification channel:

1. Enable required APIs and create a topic
2. Configure the notification channel for a topic
3. Authorize a service account
4. Set the notification channel in an alerting policy

To understand the data schema, seeSchema example.

To receive the alert notifications, you must also create one of the following subscriptions:pull,push, orBigQuery.

When the subscription is in a different project than the topic, create a service account in the subscriber project, and grant it the role ofroles/pubsub.subscriber.

Before you begin

When you add the first Pub/Sub notification channel to a Google Cloud project, Cloud Monitoring creates a service account for that project. It also grants the Identity and Access Management roleMonitoring Notification Service Agent to the service account. This service account lets Monitoring send notifications to Pub/Sub-based notification channels in this project.

The service account has the following format:

service-PROJECT_NUMBER@gcp-sa-monitoring-notification.iam.gserviceaccount.com

The name of the notifications service account includes a unique Google Cloud projectnumber. You can find the project name, ID, and number on the project's dashboard in the Google Cloud console, or you can retrieve it with the following command:

gcloud projects describePROJECT_ID --format="value(project_number)"

You can view and edit the service account by using the Google Cloud console or the Google Cloud CLI.

Enable required APIs and create a topic

In the Google Cloud project where you plan to create the notification channeland Pub/Sub topic, do the following:

Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

Roles required to select or create a project

• Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
• Create a project: To create a project, you need the Project Creator role (roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.create permission.Learn how to grant roles.

Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

Go to project selector

Verify that billing is enabled for your Google Cloud project.

Enable the Pub/Sub and Cloud Monitoring APIs.

Roles required to enable APIs

To enable APIs, you need the Service Usage Admin IAM role (roles/serviceusage.serviceUsageAdmin), which contains theserviceusage.services.enable permission.Learn how to grant roles.

Enable the APIs

In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

Roles required to select or create a project

• Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
• Create a project: To create a project, you need the Project Creator role (roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.create permission.Learn how to grant roles.

Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

Go to project selector

Verify that billing is enabled for your Google Cloud project.

Enable the Pub/Sub and Cloud Monitoring APIs.

Roles required to enable APIs

To enable APIs, you need the Service Usage Admin IAM role (roles/serviceusage.serviceUsageAdmin), which contains theserviceusage.services.enable permission.Learn how to grant roles.

Enable the APIs

1. Create a Pub/Sub topic. For information about how to create a topic, seeCreate a topic. For example, to create a topic callednotificationTopic by using the Google Cloud CLI, run the following command:

   gcloud pubsub topics create notificationTopic

For information about using the Monitoring API or the Google Cloud CLI to create the notification channel, seeCreating channels.

To use the Google Cloud console to create the notification channel, do the following:

1. In the Google Cloud console, go to thenotifications Alerting page:

   Go toAlerting

   If you use the search bar to find this page, then select the result whose subheading isMonitoring.

2. In the toolbar of the Google Cloud console,select your Google Cloud project. ForApp Hubconfigurations, select the App Hub host project or management project.
3. Select the Google Cloud project that contains the Pub/Sub topic you created.
4. ClickEdit notification channels.

5. In thePub/Sub section, clickAdd new.

   TheCreated Pub/Sub Channel dialog displays the name of the service account that Monitoring created.

6. Authorize the service account. Your service account can publish all topics or specific topics:

   • To publish all topics, selectManage roles, and add the role ofPub/Sub Publisher.

     After you complete these steps that configure the notification channel, skip the next section, which is titledAuthorize service account, and proceed toSet the notification channel in an alerting policy.

   • To publish specific topics, proceed to the next step and authorize the service account to publish specific topics after you complete configuring the notification channel. For instructions to authorize the service account, seeAuthorize service account.
7. Enter a display name for your channel and the Pub/Sub topic name.
8. (Optional) To verify that the channel is correctly configured, clickSend test notification.
9. SelectAdd channel.

Next, authorize the service account.

Authorize service account

1. In the Google Cloud console, go to theTopics page:

   Go toTopics

   If you use the search bar to find this page, then select the result whose subheading isPub/Sub.

2. In the toolbar of the Google Cloud console,select your Google Cloud project. ForApp Hubconfigurations, select the App Hub host project or management project.
3. Select the topic.
4. In thePermissions tab, selectAdd principal.
5. In theNew principal field, enter the name of the notifications service account. The service account has the following naming convention:

   service-PROJECT_NUMBER@gcp-sa-monitoring-notification.iam.gserviceaccount.com

6. Select the rolePub/Sub Publisher, and then selectSave.

To authorize your service account for a specific topic by using the Google Cloud CLI, grant thepubsub.publisher IAM role for the topic to the service account. For example, the following command configures the IAM role for thenotificationTopic topic:

gcloud pubsub topics add-iam-policy-binding \projects/PROJECT_NUMBER/topics/notificationTopic --role=roles/pubsub.publisher \--member=serviceAccount:service-PROJECT_NUMBER@gcp-sa-monitoring-notification.iam.gserviceaccount.com

A response to a successful execution of theadd-iam-policy-binding command is like the following:

 Updated IAM policy for topic [notificationTopic]. bindings: ‐ members:    ‐ serviceAccount:service-PROJECT_NUMBER@gcp-sa-monitoring-notification.iam.gserviceaccount.com    role: roles/pubsub.publisher etag: BwWcDOIw1Pc= version: 1

For more information, see thepubsub topics add-iam-policy-bindingreference page.

Authorize a service account for all topics

To authorize your service account for all topics, do the following:

1. In the Google Cloud console, go to theIAM page:

   Go toIAM

   If you use the search bar to find this page, then select the result whose subheading isIAM & Admin.

2. In the toolbar of the Google Cloud console,select your Google Cloud project. ForApp Hubconfigurations, select the App Hub host project or management project.
3. SelectInclude Google-provided role grants as shown in the following image:
   
4. Search for the service account that has the following format:

   service-PROJECT_NUMBER@gcp-sa-monitoring-notification.iam.gserviceaccount.com

   Reload the page when the service account isn't listed.

5. SelecteditEdit for the notifications service account, selectAdd another role, and then add the rolePub/Sub Publisher.

Next, set the notification channel in an alerting policy.

Set the notification channel in an alerting policy

To use a Pub/Sub notification channel in an alerting policy, selectPub/Sub as the channel type, and then select the topic.

Schema example

To view an example JSON packet and the schema, expand the following sections.

{  "incident": {    "incident_id": "0.opqiw61fsv7p",    "renotify": true,    "scoping_project_id": "internal-project",    "scoping_project_number": 12345,    "url": "https://console.cloud.google.com/monitoring/alerting/incidents/0.lxfiw61fsv7p?project=internal-project",    "severity": "no severity",    "started_at": 1577840461,    "ended_at": 1577877071,    "state": "closed",    "resource_id": "11223344",    "resource_name": "internal-project gke-cluster-1-default-pool-e2df4cbd-dgp3",    "resource_display_name": "gke-cluster-1-default-pool-e2df4cbd-dgp3",    "resource_type_display_name": "VM Instance",    "resource": {      "type": "gce_instance",      "labels": {        "instance_id": "11223344",        "project_id": "internal-project",        "zone": "us-central1-c"      }    },    "metric": {      "type": "compute.googleapis.com/instance/cpu/utilization",      "displayName": "CPU utilization",      "labels": {        "instance_name": "the name of the VM instance"      }    },    "metadata": {      "system_labels": { "labelkey": "labelvalue" },      "user_labels": { "labelkey": "labelvalue" }    },    "policy_name": "Monitor-Project-Cluster",    "policy_user_labels" : {        "user-label-1" : "important label",        "user-label-2" : "another label"    },    "condition_name": "VM Instance - CPU utilization [MAX]",    "threshold_value": "0.9",    "observed_value": "0.835",    "condition": {      "name": "projects/internal-project/alertPolicies/1234567890123456789/conditions/1234567890123456789",      "displayName": "VM Instance - CPU utilization [MAX]",      "conditionThreshold": {        "filter": "metric.type=\"compute.googleapis.com/instance/cpu/utilization\" resource.type=\"gce_instance\" metadata.system_labels.\"state\"=\"ACTIVE\"",        "aggregations": [          {            "alignmentPeriod": "120s",            "perSeriesAligner": "ALIGN_MEAN"          }        ],        "comparison": "COMPARISON_GT",        "thresholdValue": 0.9,        "duration": "0s",        "trigger": {          "count": 1        }      }    },    "documentation": {      "content": "TEST ALERT\n\npolicy.name=projects/internal-project/alertPolicies/1234567890123456789\n\npolicy.display_name=Monitored-Project-NO-GROUPBY\n\ncondition.name=projects/nternal-project/alertPolicies/1234567890123456789/conditions/1234567890123456789\n\ncondition.display_name=VM Instance - CPU utilization [MAX]\n\nproject=internal-project\n\nresrouce.project=internal-project \n\nDONE\n",      "mime_type": "text/markdown",      "subject": "ALERT - No severity",      "links": [        {          "displayName": "Playbook",          "url": "https://myownpersonaldomain.com/playbook?name=${resource.name}"        }      ]    },    "summary": "CPU utilization for internal-project gke-cluster-1-16-default-pool-e2df4cbd-dgp3 with metric labels {instance_name=gke-cluster-1-default-pool-e2df4cbd-dgp3} and system labels {state=ACTIVE} returned to normal with a value of 0.835."  },  "version": "1.2"}

Deprecation policy

Google Chat

Preview

This product or feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of theService Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see thelaunch stage descriptions.

The Google Cloud Monitoring app allows your Google Chat spaces toreceive notifications.

Before you begin

If you are in an organization, then to install theGoogle Cloud Monitoring app, you must have access to theGoogle Cloud Monitoring app. If you don't have access, thenrequest that a Google Workspace administrator do the following:

1. Add the app to the Marketplace apps allowlist and enable access at the top organizational unit.
2. Configure Marketplace app user install settings so that users can install the app.

Install the Google Cloud Monitoring app

You must use the following procedure to install theGoogle Cloud Monitoring app. Installation from theGoogle Workspace Marketplace listingisn't supported.

To install the app and configure a space as anotification channel, do the following:

1. In Google Chat, open or create the space where you want toreceive notifications.

2. Install the Google Cloud Monitoring app:

   1. Select your space name and then selectApps and Integrations.

   2. If the Google Cloud Monitoring app doesn't appear in the Apps list,then return to your space, enter@Google Cloud Monitoring, and thenpressEnter.

   3. ClickAdd to space.

3. Copy the chat space ID to your clipboard.

   If you installed the Google Cloud Monitoring app, then the chat space ID is included in the installation confirmation. Otherwise, you can find the chat space ID as the series of numbers and letters followingspace/ at the end of your chat space URL.

4. Open a new browser tab and then configure the notification channel:

   1. In the Google Cloud console, go to thenotifications Alerting page:

      Go toAlerting

      If you use the search bar to find this page, then select the result whose subheading isMonitoring.

   2. In the toolbar of the Google Cloud console,select your Google Cloud project. ForApp Hubconfigurations, select the App Hub host project or management project.

   3. ClickEdit notification channels.

   4. Go to theGoogle Chat section and clickAdd New.

   5. Enter your chat space ID in theChat Space ID field and then clickSave.