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 the name field with that [CONDITION_ID]. If the supplied condition omits the name field, then a new [CONDITION_ID] is created.
Required. The updated alerting policy or the updated values for the fields listed in update_mask. If update_mask is not empty, any fields in this policy that are not in update_mask are ignored.
getUpdateMask
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 the name field with that
[CONDITION_ID]. If the supplied condition omits the name field,
then a new [CONDITION_ID] is created.
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 the name field with that
[CONDITION_ID]. If the supplied condition omits the name field,
then a new [CONDITION_ID] is created.
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 the name field with that
[CONDITION_ID]. If the supplied condition omits the name field,
then a new [CONDITION_ID] is created.
Required. The updated alerting policy or the updated values for the
fields listed in update_mask.
If update_mask is not empty, any fields in this policy that are
not in update_mask are ignored.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Stackdriver Monitoring V3 Client - Class UpdateAlertPolicyRequest (2.1.2)\n\nVersion latestkeyboard_arrow_down\n\n- [2.1.2 (latest)](/php/docs/reference/cloud-monitoring/latest/V3.UpdateAlertPolicyRequest)\n- [2.1.1](/php/docs/reference/cloud-monitoring/2.1.1/V3.UpdateAlertPolicyRequest)\n- [2.0.1](/php/docs/reference/cloud-monitoring/2.0.1/V3.UpdateAlertPolicyRequest)\n- [1.12.1](/php/docs/reference/cloud-monitoring/1.12.1/V3.UpdateAlertPolicyRequest)\n- [1.11.1](/php/docs/reference/cloud-monitoring/1.11.1/V3.UpdateAlertPolicyRequest)\n- [1.10.3](/php/docs/reference/cloud-monitoring/1.10.3/V3.UpdateAlertPolicyRequest)\n- [1.9.0](/php/docs/reference/cloud-monitoring/1.9.0/V3.UpdateAlertPolicyRequest)\n- [1.8.0](/php/docs/reference/cloud-monitoring/1.8.0/V3.UpdateAlertPolicyRequest)\n- [1.7.1](/php/docs/reference/cloud-monitoring/1.7.1/V3.UpdateAlertPolicyRequest)\n- [1.6.0](/php/docs/reference/cloud-monitoring/1.6.0/V3.UpdateAlertPolicyRequest)\n- [1.5.1](/php/docs/reference/cloud-monitoring/1.5.1/V3.UpdateAlertPolicyRequest)\n- [1.4.0](/php/docs/reference/cloud-monitoring/1.4.0/V3.UpdateAlertPolicyRequest)\n- [1.3.2](/php/docs/reference/cloud-monitoring/1.3.2/V3.UpdateAlertPolicyRequest)\n- [1.2.2](/php/docs/reference/cloud-monitoring/1.2.2/V3.UpdateAlertPolicyRequest) \nReference documentation and code samples for the Stackdriver Monitoring V3 Client class UpdateAlertPolicyRequest.\n\nThe protocol for the `UpdateAlertPolicy` request.\n\nGenerated from protobuf message `google.monitoring.v3.UpdateAlertPolicyRequest`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Monitoring \\\\ V3\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getUpdateMask\n\nOptional. A list of alerting policy field names. If this field is not\nempty, each listed field in the existing alerting policy is set to the\nvalue of the corresponding field in the supplied policy (`alert_policy`),\nor to the field's default value if the field is not in the supplied\nalerting policy. Fields not listed retain their previous value.\n\nExamples of valid field masks include `display_name`, `documentation`,\n`documentation.content`, `documentation.mime_type`, `user_labels`,\n`user_label.nameofkey`, `enabled`, `conditions`, `combiner`, etc.\nIf this field is empty, then the supplied alerting policy replaces the\nexisting policy. It is the same as deleting the existing policy and\nadding the supplied policy, except for the following:\n\n- 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.\n- Conditions in the new policy will keep their former `[CONDITION_ID]` if the supplied condition includes the `name` field with that `[CONDITION_ID]`. If the supplied condition omits the `name` field, then a new `[CONDITION_ID]` is created.\n\n### hasUpdateMask\n\n### clearUpdateMask\n\n### setUpdateMask\n\nOptional. A list of alerting policy field names. If this field is not\nempty, each listed field in the existing alerting policy is set to the\nvalue of the corresponding field in the supplied policy (`alert_policy`),\nor to the field's default value if the field is not in the supplied\nalerting policy. Fields not listed retain their previous value.\n\nExamples of valid field masks include `display_name`, `documentation`,\n`documentation.content`, `documentation.mime_type`, `user_labels`,\n`user_label.nameofkey`, `enabled`, `conditions`, `combiner`, etc.\nIf this field is empty, then the supplied alerting policy replaces the\nexisting policy. It is the same as deleting the existing policy and\nadding the supplied policy, except for the following:\n\n- 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.\n- Conditions in the new policy will keep their former `[CONDITION_ID]` if the supplied condition includes the `name` field with that `[CONDITION_ID]`. If the supplied condition omits the `name` field, then a new `[CONDITION_ID]` is created.\n\n### getAlertPolicy\n\nRequired. The updated alerting policy or the updated values for the\nfields listed in `update_mask`.\n\nIf `update_mask` is not empty, any fields in this policy that are\nnot in `update_mask` are ignored.\n\n### hasAlertPolicy\n\n### clearAlertPolicy\n\n### setAlertPolicy\n\nRequired. The updated alerting policy or the updated values for the\nfields listed in `update_mask`.\n\nIf `update_mask` is not empty, any fields in this policy that are\nnot in `update_mask` are ignored.\n\n### static::build"]]
