Skip to main content

alert_policies

Creates, updates, deletes, gets or lists a alert_policies resource.

Overview

Namealert_policies
TypeResource
Idgoogle.monitoring.alert_policies

Fields

NameDatatypeDescription
namestringIdentifier. Required if the policy exists. The resource name for this policy. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[ALERT_POLICY_ID][ALERT_POLICY_ID] is assigned by Cloud Monitoring when the policy is created. When calling the alertPolicies.create method, do not include the name field in the alerting policy passed as part of the request.
alertStrategyobjectControl over how the notification channels in notification_channels are notified when this alert fires.
combinerstringHow to combine the results of multiple conditions to determine if an incident should be opened. If condition_time_series_query_language is present, this must be COMBINE_UNSPECIFIED.
conditionsarrayA list of conditions for the policy. The conditions are combined by AND or OR according to the combiner field. If the combined conditions evaluate to true, then an incident is created. A policy can have from one to six conditions. If condition_time_series_query_language is present, it must be the only condition. If condition_monitoring_query_language is present, it must be the only condition.
creationRecordobjectDescribes a change made to a configuration.
displayNamestringA short name or phrase used to identify the policy in dashboards, notifications, and incidents. To avoid confusion, don't use the same display name for multiple policies in the same project. The name is limited to 512 Unicode characters.The convention for the display_name of a PrometheusQueryLanguageCondition is "{rule group name}/{alert name}", where the {rule group name} and {alert name} should be taken from the corresponding Prometheus configuration file. This convention is not enforced. In any case the display_name is not a unique key of the AlertPolicy.
documentationobjectDocumentation that is included in the notifications and incidents pertaining to this policy.
enabledbooleanWhether or not the policy is enabled. On write, the default interpretation if unset is that the policy is enabled. On read, clients should not make any assumption about the state if it has not been populated. The field should always be populated on List and Get operations, unless a field projection has been specified that strips it out.
mutationRecordobjectDescribes a change made to a configuration.
notificationChannelsarrayIdentifies the notification channels to which notifications should be sent when incidents are opened or closed or when new violations occur on an already opened incident. Each element of this array corresponds to the name field in each of the NotificationChannel objects that are returned from the ListNotificationChannels method. The format of the entries in this field is: projects/[PROJECT_ID_OR_NUMBER]/notificationChannels/[CHANNEL_ID]
severitystringOptional. The severity of an alert policy indicates how important incidents generated by that policy are. The severity level will be displayed on the Incident detail page and in notifications.
userLabelsobjectUser-supplied key/value data to be used for organizing and identifying the AlertPolicy objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.Note that Prometheus {alert name} is a valid Prometheus label names (https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels), whereas Prometheus {rule group} is an unrestricted UTF-8 string. This means that they cannot be stored as-is in user labels, because they may contain characters that are not allowed in user-label values.
validityobjectThe Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC (https://github.com/grpc). Each Status message contains three pieces of data: error code, error message, and error details.You can find out more about this error model and how to work with it in the API Design Guide (https://cloud.google.com/apis/design/errors).

Methods

NameAccessible byRequired ParamsDescription
projects_alert_policies_getSELECTalertPoliciesId, projectsIdGets a single alerting policy.
projects_alert_policies_listSELECTprojectsIdLists the existing alerting policies for the workspace.
projects_alert_policies_createINSERTprojectsIdCreates a new alerting policy.Design your application to single-thread API calls that modify the state of alerting policies in a single project. This includes calls to CreateAlertPolicy, DeleteAlertPolicy and UpdateAlertPolicy.
projects_alert_policies_deleteDELETEalertPoliciesId, projectsIdDeletes an alerting policy.Design your application to single-thread API calls that modify the state of alerting policies in a single project. This includes calls to CreateAlertPolicy, DeleteAlertPolicy and UpdateAlertPolicy.
projects_alert_policies_patchUPDATEalertPoliciesId, projectsIdUpdates an alerting policy. You can either replace the entire policy with a new one or replace only certain fields in the current alerting policy by specifying the fields to be updated via updateMask. Returns the updated alerting policy.Design your application to single-thread API calls that modify the state of alerting policies in a single project. This includes calls to CreateAlertPolicy, DeleteAlertPolicy and UpdateAlertPolicy.

SELECT examples

Lists the existing alerting policies for the workspace.

SELECT
name,
alertStrategy,
combiner,
conditions,
creationRecord,
displayName,
documentation,
enabled,
mutationRecord,
notificationChannels,
severity,
userLabels,
validity
FROM google.monitoring.alert_policies
WHERE projectsId = '{{ projectsId }}';

INSERT example

Use the following StackQL query and manifest file to create a new alert_policies resource.

/*+ create */
INSERT INTO google.monitoring.alert_policies (
projectsId,
name,
displayName,
documentation,
userLabels,
conditions,
combiner,
enabled,
validity,
notificationChannels,
creationRecord,
mutationRecord,
alertStrategy,
severity
)
SELECT
'{{ projectsId }}',
'{{ name }}',
'{{ displayName }}',
'{{ documentation }}',
'{{ userLabels }}',
'{{ conditions }}',
'{{ combiner }}',
{{ enabled }},
'{{ validity }}',
'{{ notificationChannels }}',
'{{ creationRecord }}',
'{{ mutationRecord }}',
'{{ alertStrategy }}',
'{{ severity }}'
;

UPDATE example

Updates a alert_policies resource.

/*+ update */
UPDATE google.monitoring.alert_policies
SET
name = '{{ name }}',
displayName = '{{ displayName }}',
documentation = '{{ documentation }}',
userLabels = '{{ userLabels }}',
conditions = '{{ conditions }}',
combiner = '{{ combiner }}',
enabled = true|false,
validity = '{{ validity }}',
notificationChannels = '{{ notificationChannels }}',
creationRecord = '{{ creationRecord }}',
mutationRecord = '{{ mutationRecord }}',
alertStrategy = '{{ alertStrategy }}',
severity = '{{ severity }}'
WHERE
alertPoliciesId = '{{ alertPoliciesId }}'
AND projectsId = '{{ projectsId }}';

DELETE example

Deletes the specified alert_policies resource.

/*+ delete */
DELETE FROM google.monitoring.alert_policies
WHERE alertPoliciesId = '{{ alertPoliciesId }}'
AND projectsId = '{{ projectsId }}';