This page illustrates using the Stackdriver Monitoring console to create, edit, and manage alerting policies using the new UI (Beta).
An alerting policy describes a set of conditions indicating a potentially unhealthy status in your system. Alerting policies can reference notification channels, which let you specify how you want to be informed that an alerting policy has been triggered. Alerting policies can also include documentation that will assist responders in handling the situation.
Before you begin
Before creating alerting policies, you should be familiar with the general concepts and terminology used with alerting policies; see Introduction to Alerting for more information.
Trying the new UI (Beta)
The Alerting UI is moving to a new implementation. Currently, both versions are available. You can choose to use the current UI or you can choose to use the new UI. With the new UI, you will be able to define conditions using the same metric picker that Metrics Explorer uses.
If you choose to opt in, you will be able to define conditions using the same metric picker that Metrics Explorer uses. This page describes the new UI.
Why try it?
The Beta interface serves the same purpose as the current UI, but your ability to precisely tailor metrics to your needs is much greater.
- You have options for filtering, alignment, and aggregation the Target metric that the other variant hides.
- You can more precisely specify the behavior the metric must exhibit for the condition to be met, in the Configuration area.
- You can create conditions based on custom and logs-based metrics.
- You have access to metadata-filtering options.
- You can edit conditions created with the API that cannot be edited with the current UI.
With the Beta UI, you can create metric-absence conditions and most types of metric-threshold conditions.
You cannot create process-health conditions with the Beta UI. These health policies are created using the current UI. You can also use the API.
If you create or edit conditions with the new UI, you might not be able to edit them with the current UI.
Staying with the current UI
If you decide not to try the new UI, you continue to use the existing UI, which provides a number of condition types with many options set for you. See Overview for information on this interface. If you opt into the new UI, you can always change your mind.
Creating an alerting policy
On the Google Cloud Platform Console, choose your project from the drop-down list and select Stackdriver > Monitoring from the menu on the left side. On the Monitoring console, select Alerting > Create a Policy:
This brings up the Create New Alerting Policy page, which offers four options:
The following sections describe each of these options.
Conditions describe the circumstances under which the policy will be triggered. A policy can have up to 6 conditions.
If you are editing a policy that already has conditions, these conditions are listed. Existing conditions can be edited or deleted.
To add an alerting condition to a policy, expand the Conditions dialog in the Create New Alerting Policy page. Next, click the Add Condition button to bring up the following page:
For detailed information on how to select the resource type, the metric and the configuration, see Specifying Conditions (Beta).
Notification channels let you specify how you want to be informed of alerts. Configuring a notification channel is optional. To add a notification channel to your policy, click the Notifications button in the Create New Alerting Policy page:
Click Add Notification Channel:
Click the drop-down icon and select a notification channel:
After you have selected the channel, the UI will ask you for additional information that is specific to the type of channel you selected. For example, if you selected Email, the UI presents the button Add Email Address. Click this button and enter your information:
See Notification Options for details on your choices of notification channels.
You can use multiple notification channels in a policy. Having at least two different types of notification channel increases reliability in case one is unavailable. To add additional channels, click the Add Notification Channel button.
Documentation is optional information that is sent along with notifications to help the recipients handle the condition. To add documentation, click the Add Documentation button in the Create New Alerting Policy page. This gives you an editable field for your documentation.
You can use Markdown in this field to format your documentation. For example:
In addition to Markdown, you can use variables to pull information out of the policy itself, to tailor the content of your documentation. See Using variables for more information. You can also include channel-specific tagging to control notifications. See Using channel controls for more information.
Name the policy
To name your policy, click the Name this policy button in the Create New Alerting Policy page. This page gives you an editable field for a descriptive policy name:
Save the policy
When you are ready to save your policy, click the Save button at the bottom of the page.
To manage a policy, select your Workspace, then select Alerting > Policies Overview. This brings up a summary of all the policies, along with the status of the policy and any incidents. The following screenshot shows a single policy from the overview:
From the Overview page, you can edit, copy, or delete policies.
To edit a policy, click the Edit button. This brings up the Edit alerting policy page, which works exactly like the page for creating policies, described in Creating an alerting policy.
From the Overview pages, you can also enable or disable policies. Each policy has an On/Off button next to it. Click the button to toggle the state of the alerting policy.