Settings for common alerting policies

To create an alerting policy, you must describe what is to be monitored, when the alerting policy is triggered, and how you want to be notified. This page contains settings that you can use to create alerting policies. Most sections in this page have the following elements:

• Title: Lists the relevant product name and a brief description of the alerting policy.
• Summary: A brief description of the alerting policy. For full information, see the product documentation.
• Steps to create an alerting policy: Outline of the steps required to create an alerting policy. For detailed information on these steps, see Creating an alerting policy.

• Target-pane fields: These fields specify what is being monitored and how the data is aggregated. If you are using the Google Cloud console, these are the fields in the Target pane of the Add Condition dialog.

• Configuration fields: These fields specify when the alerting policy triggers. By changing the duration window, you can reduce how often a policy triggers. If you are using the Google Cloud console, these are the fields in the Configuration pane of the Add Condition dialog.

When you only want to configure a chart, use the table with the target-pane fields to help you configure the chart. Alerting conditions, Metrics Explorer, and Dashboard editor use slightly different notation:

Field name in the target pane table	Dashboard editor (Advanced tab)	Metrics Explorer	Alerting policies (Legacy)	Alerting policies (Preview)
Aligner	Alignment function	Aligner	Aligner	Rolling window function
Period	Alignment period	Minimum alignment period	Period	Rolling window
Group by	Group By	Group By	Group By	Time series group by
Aggregator	Group by function	Aggregator	Aggregator	Time series aggregation

Note: If you create alerting policies with the legacy editor, then ignore the references to the Metric category in this document. That field isn't relevant when you use the legacy editor.

Billing

To be notified if your billable or forecasted charges exceed a budget, create an alert by using the Budgets and alerts page of the Google Cloud console:

1. Sign in to the Google Cloud console:
   Sign in to Google Cloud console
2. Open the console Navigation menu , and then select Billing. If you have more than one Cloud Billing account, then do one of the following:
   • To manage Cloud Billing for the current project, select Go to linked billing account.
   • To locate a different Cloud Billing account, select Manage billing accounts and choose the account for which you'd like to set a budget.
3. In the Billing navigation menu, select Budgets & alerts.
4. Click Create budget.
5. Complete the budget dialog. In this dialog, you select Google Cloud projects and products, and then you create a budget for that combination. By default, you are notified when you reach 50%, 90%, and 100% of the budget. For complete documentation, see Set budgets and budget alerts.
   Note: In the billing dialog, the Google Cloud's operations suite products are prefixed with "Stackdriver". If you want an alert on Cloud Monitoring usage, then select Stackdriver Monitoring.

BigQuery execution time

To create an alerting policy that triggers when the 99th percentile of the execution time of a BigQuery query exceeds a user-defined limit, use the following settings.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select BigQuery Project. In the Metric categories menu, select Query. In the Metrics menu, select Query execution times.
Filter
Group by	priority
Aggregator	99th percentile
Period	5 m
Aligner	sum

Configure alert trigger Field	Value
Condition type	Threshold
Alert trigger	Any time series violates
Threshold position	Above threshold
Threshold value	You determine this value; however, a threshold of 60 seconds is recommended.
Retest window	most recent value

BigQuery usage

To create an alerting policy that triggers when the ingested BigQuery metrics exceed a user-defined level, use the following settings.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select BigQuery Dataset. In the Metric categories menu, select Storage. Select a metric from the Metrics menu. Metrics specific to usage include Stored bytes, Uploaded bytes, and Uploaded bytes billed. For a full list of available metrics, see BigQuery metrics.
Filter	project_id: Your Google Cloud project ID. dataset_id: Your dataset ID.
Group By	dataset_id: Your dataset ID.
Aggregator	sum
Period	1 m
Aligner	mean

Configure alert trigger Field	Value
Condition type	Threshold
Alert trigger	Any time series violates
Threshold position	Above threshold
Threshold value	You determine the acceptable value.
Retest window	1 minute

Compute Engine early boot validation

Early Boot Validation shows the pass/fail status of the early boot portion of the last boot sequence. Early boot is the boot sequence from the start of the UEFI firmware until it passes control to the bootloader.

To create an alerting policy that triggers when the early boot sequence fails for any of your Compute Engine VM instances, use the following settings.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select VM Instance. In the Metric categories menu, select Instance. In the Metrics menu, select Early boot validation.
Filter	status = failed
Group By	status
Aggregator	sum
Period	Use default.
Aligner	Use default

Configure alert trigger Field	Value
Condition type	Threshold
Alert trigger	Any time series violates
Threshold position	Above threshold
Threshold value	0
Retest window	1 minute

Compute Engine late boot validation

Late Boot Validation shows the pass/fail status of the late boot portion of the last boot sequence. Late boot is the boot sequence from the bootloader until completion. This includes the loading of the operating system kernel.

To create an alerting policy that triggers when the late boot sequence fails for any of your Compute Engine VM instances, use the following settings.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select VM Instance. In the Metric categories menu, select Instance. In the Metrics menu, select Late boot validation.
Filter	status = failed
Group By	status
Aggregator	sum
Period	Use default.
Aligner	Use default

Configure alert trigger Field	Value
Condition type	Threshold
Alert trigger	Any time series violates
Threshold position	Above threshold
Threshold value	0
Retest window	1 minute

Logging monthly log bytes ingested

To create an alerting policy that triggers when your monthly log bytes ingested exceeds your user-defined limit for Cloud Logging, use the following settings.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select Global. In the Metric categories menu, select Logs-based metric. In the Metrics menu, select Monthly log bytes ingested.
Filter
Aggregator	sum
Period	60 m
Aligner	max

Configure alert trigger Field	Value
Condition type	Threshold
Alert trigger	Any time series violates
Threshold position	Above threshold
Threshold value	You determine the acceptable value.
Retest window	Minimum acceptable value is 30 minutes.

Recommendations AI prediction

To set up a Recommendations AI prediction alert, use the following settings in the alerting policy.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select Consumed API. In the Metric categories menu, select Api. In the Metrics menu, select Request count.
Filter	service = recommendationengine.googleapis.com method = google.cloud.recommendationengine.v1beta1.PredictionService.Predict response_code != 200
Aggregator	sum
Period	1 m
Aligner	sum

Configure alert trigger Field	Value
Condition type	Threshold
Alert trigger	Any time series violates
Threshold position	Above threshold
Threshold value	0
Retest window	5 minutes

Recommendations AI user event recording reduction

To set up a Recommendations AI event recording reduction alert, use the following settings in the alerting policy.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select Consumed API. In the Metric categories menu, select Api. In the Metrics menu, select Request count.
Filter	service = recommendationengine.googleapis.com method = google.cloud.recommendationengine.v1beta1.PredictionService.CollectUserEvent response_code != 200
Aggregator	sum
Period	1 m
Aligner	sum

Configure alert trigger Field	Value
Condition type	Metric absence
Alert trigger	Any time series violates
Trigger absence time	10 minutes

Spanner high priority CPU usage

To create an alerting policy that triggers when your high priority cpu utilization for Cloud Spanner is above a recommended threshold, use the following settings.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select Cloud Spanner Instance. In the Metric categories menu, select Instance. In the Metrics menu, select CPU Utilization by priority. (The metric.type is spanner.googleapis.com/instance/cpu/utilization_by_priority).
Filter	instance_id = YOUR_INSTANCE_ID priority = high
Group By	location for multi-region instances; leave it blank for regional instances.
Aggregator	sum
Period	10 m
Aligner	mean

Configure alert trigger Field	Value
Condition type	Threshold
Alert trigger	Any time series violates
Threshold position	Above threshold
Threshold value	45% for multi-region instances; 65% for regional instances.
Retest window	10 minutes

Spanner 24 hour rolling usage

To create an alerting policy that triggers when the 24 hour rolling average of your cpu utilization for Cloud Spanner is above a recommended threshold, use the following settings.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select Cloud Spanner Instance. In the Metric categories menu, select Instance. In the Metrics menu, select Smoothed CPU utilization. (The metric.type is spanner.googleapis.com/instance/cpu/smoothed_utilization).
Filter	instance_id = YOUR_INSTANCE_ID
Aggregator	sum
Period	10 m
Aligner	mean

Configure alert trigger Field	Value
Condition type	Threshold
Alert trigger	Any time series violates
Threshold position	Above threshold
Threshold	90%
Retest window	10 minutes

Spanner storage

To create an alerting policy that triggers when your storage for your Cloud Spanner instance is above a recommended threshold, use the following settings.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select Cloud Spanner Instance. In the Metric categories menu, select Instance. In the Metrics menu, select Storage used. (The metric.type is spanner.googleapis.com/instance/storage/used_bytes).
Filter	instance_id = YOUR_INSTANCE_ID
Aggregator	sum
Period	10 m
Aligner	max

Configure alert trigger Field	Value
Condition type	Threshold
Condition triggers if	Any time series violates
Threshold position	Above threshold
Threshold value	Set the threshold to 75% of the maximum storage per node, multiplied by the number of nodes. For the current node limits, see Cloud Spanner Quotas & limits.
Retest window	10 minutes

Trace over quota on API usage

To create an alerting policy that triggers when your monthly Cloud Trace spans ingested exceeds your quota, use the following settings.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select Consumed API. In the Metric categories menu, select Api. In the Metrics menu, select Request count. (The metric.type is serviceruntime.googleapis.com/api/request_count).
Filter	service = cloudtrace.googleapis.com response_code = 429
Aggregator	sum
Period	1 m
Aligner	sum

Configure alert trigger Field	Value
Condition type	Threshold
Alert trigger	Any time series violates
Threshold position	Above threshold
Threshold value	0
Retest window	1 minute

Trace monitor monthly span-usage

To create an alerting policy that triggers when your monthly Cloud Trace spans ingested exceeds a user-defined limit, use the following settings.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select Global. In the Metric categories menu, select Billing. In the Metrics menu, select Monthly trace spans ingested.
Filter
Aggregator	sum
Period	60 m
Aligner	max

Configure alert trigger Field	Value
Condition type	Threshold
Alert trigger	Any time series violates
Threshold position	Above threshold
Threshold value	You determine the acceptable value.
Retest window	Minimum acceptable value is 30 minutes.

Trace export errors

To create an alerting policy that triggers if there are errors exporting Cloud Trace data to BigQuery, use the following settings.

The following tables are for the preview alerting interface. You can use these tables if you are using the legacy interface; however, some fields have slightly different names. These tables specify a value for the Metric category menu. This menu isn't relevant when you use the legacy alerting interface. For infromation about using the legacy alerting interafce, see Create an alerting policy.

Steps to create an alerting policy.

To create an alerting policy using the preview interface, do the following:

1. In the Google Cloud console, go to Monitoring or use the following button:
   Go to Monitoring
2. In the Monitoring navigation pane, select Alerting and then select Create Policy.
3. Select your metric, add filters, and specify how the data is transformed. To complete these steps, use the values in the Target table. To select the metric, expand the Select a metric menu and then do the following:
   1. (Optional) To limit the menu to relevant entries, enter the resource or metric name in the filter bar.
   2. Select a Resource type. For example, select VM instance.
   3. Select a Metric category. For example, select instance.
   4. Select a Metric. For example, select CPU Utilization.
   5. Select Apply.
4. Click Next and then configure the alerting policy trigger. To complete these fields, use the values in the Configure alert trigger table.
5. Click Next and add notifications to your alerting policy:
   1. Click Notification channels.

   2. Select one or more notification channels from the menu.

      If a notification channel that you want to add isn't listed, then click Manage notification channels. You are taken to the Notification channels page in a new browser tab. From this page, you can update the configured notification channels. After you have completed your updates, return to the original tab, click Refresh , and then select the notification channels to add to the alerting policy.

   3. Click OK.
   4. (Optional) To be notified when incidents are openend and closed, check Notify on incident closure. By default, notifications are sent only when incidents are openend.
   5. (Optional) Update the Incident autoclose duration. This field determines when Monitoring closes incidents in the absence of metric data.
6. (Optional) Enter any information that you want included in a notification message into the Documentation section.
7. Click Name and enter a name for the alerting policy.
8. Click Next, review your settings, and then click Create policy.

Target Field	Value
Resource and Metric	In the Resources menu, select Cloud Trace. In the Metric categories menu, select Bigquery_export. In the Metrics menu, select Spans Exported to BigQuert.
Filter	status != ok
Group by	status
Aggregator	sum
Period	1 m
Aligner	rate

Configure alert trigger Field	Value
Condition type	Threshold
Alert trigger	Any time series violates
Threshold position	Above threshold
Threshold value	0
Retest window	1 minute

Uptime check monitoring

To create an alerting policy for an uptime check, or to create a chart that displays the success or latency status of an uptime check, see Alerting on uptime checks.