Reference documentation and code samples for the Cloud Monitoring V3 API class Google::Cloud::Monitoring::V3::UpdateAlertPolicyRequest.
The protocol for the UpdateAlertPolicy
request.
Inherits
- Object
Extended By
- Google::Protobuf::MessageExts::ClassMethods
Includes
- Google::Protobuf::MessageExts
Methods
#alert_policy
def alert_policy() -> ::Google::Cloud::Monitoring::V3::AlertPolicy
-
(::Google::Cloud::Monitoring::V3::AlertPolicy) — Required. The updated alerting policy or the updated values for the
fields listed in
update_mask
. Ifupdate_mask
is not empty, any fields in this policy that are not inupdate_mask
are ignored.
#alert_policy=
def alert_policy=(value) -> ::Google::Cloud::Monitoring::V3::AlertPolicy
-
value (::Google::Cloud::Monitoring::V3::AlertPolicy) — Required. The updated alerting policy or the updated values for the
fields listed in
update_mask
. Ifupdate_mask
is not empty, any fields in this policy that are not inupdate_mask
are ignored.
-
(::Google::Cloud::Monitoring::V3::AlertPolicy) — Required. The updated alerting policy or the updated values for the
fields listed in
update_mask
. Ifupdate_mask
is not empty, any fields in this policy that are not inupdate_mask
are ignored.
#update_mask
def update_mask() -> ::Google::Protobuf::FieldMask
-
(::Google::Protobuf::FieldMask) —
Optional. A list of alerting policy field names. If this field is not empty, each listed field in the existing alerting policy is set to the value of the corresponding field in the supplied policy (
alert_policy
), or to the field's default value if the field is not in the supplied alerting policy. Fields not listed retain their previous value.Examples of valid field masks include
display_name
,documentation
,documentation.content
,documentation.mime_type
,user_labels
,user_label.nameofkey
,enabled
,conditions
,combiner
, etc.If this field is empty, then the supplied alerting policy replaces the existing policy. It is the same as deleting the existing policy and adding the supplied policy, except for the following:
- The new policy will have the same
[ALERT_POLICY_ID]
as the former policy. This gives you continuity with the former policy in your notifications and incidents. - Conditions in the new policy will keep their former
[CONDITION_ID]
if the supplied condition includes thename
field with that[CONDITION_ID]
. If the supplied condition omits thename
field, then a new[CONDITION_ID]
is created.
- The new policy will have the same
#update_mask=
def update_mask=(value) -> ::Google::Protobuf::FieldMask
-
value (::Google::Protobuf::FieldMask) —
Optional. A list of alerting policy field names. If this field is not empty, each listed field in the existing alerting policy is set to the value of the corresponding field in the supplied policy (
alert_policy
), or to the field's default value if the field is not in the supplied alerting policy. Fields not listed retain their previous value.Examples of valid field masks include
display_name
,documentation
,documentation.content
,documentation.mime_type
,user_labels
,user_label.nameofkey
,enabled
,conditions
,combiner
, etc.If this field is empty, then the supplied alerting policy replaces the existing policy. It is the same as deleting the existing policy and adding the supplied policy, except for the following:
- The new policy will have the same
[ALERT_POLICY_ID]
as the former policy. This gives you continuity with the former policy in your notifications and incidents. - Conditions in the new policy will keep their former
[CONDITION_ID]
if the supplied condition includes thename
field with that[CONDITION_ID]
. If the supplied condition omits thename
field, then a new[CONDITION_ID]
is created.
- The new policy will have the same
-
(::Google::Protobuf::FieldMask) —
Optional. A list of alerting policy field names. If this field is not empty, each listed field in the existing alerting policy is set to the value of the corresponding field in the supplied policy (
alert_policy
), or to the field's default value if the field is not in the supplied alerting policy. Fields not listed retain their previous value.Examples of valid field masks include
display_name
,documentation
,documentation.content
,documentation.mime_type
,user_labels
,user_label.nameofkey
,enabled
,conditions
,combiner
, etc.If this field is empty, then the supplied alerting policy replaces the existing policy. It is the same as deleting the existing policy and adding the supplied policy, except for the following:
- The new policy will have the same
[ALERT_POLICY_ID]
as the former policy. This gives you continuity with the former policy in your notifications and incidents. - Conditions in the new policy will keep their former
[CONDITION_ID]
if the supplied condition includes thename
field with that[CONDITION_ID]
. If the supplied condition omits thename
field, then a new[CONDITION_ID]
is created.
- The new policy will have the same