imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 23:08:48 +00:00
Code Activity

gcloud: Wed May 14 10:45:02 UTC 2025

Browse source
This commit is contained in:
Automated 2025-05-14 10:45:02 +00:00
parent dfebca5b6c
commit 82f3a66664
423 changed files with 11160 additions and 1149 deletions
Download patch file Download diff file Expand all files Collapse all files

21
gcloud/monitoring/snoozes/create
View file

@ -50,15 +50,20 @@ FLAGS
in the --snooze-from-file flags if specified.
--criteria-filter=CRITERIA_FILTER
The filter that the Snooze applies to, which is a string to match on
Alert fields when silencing the alerts. It follows the standard
https://google.aip.dev/160 syntax. Filters can be defined for snoozes
that apply to one alerting policy. Filters must be a string formatted
as one or more resource labels with specific label values. If
multiple resource labels are used, then they must be connected with
an AND operator. For example:
Optional. When you define a Snooze, you can also define a filter for
that snooze. The filter is a string containing one or more key-value
pairs. The string uses the standard https://google.aip.dev/160 filter
syntax. If you define a filter for a snooze, then the snooze can only
apply to one alert policy. When the snooze is active, incidents won't
be created when the incident would have key-value pairs (labels) that
match those specified by the filter in the snooze. Snooze filters
support resource, metric, and metadata labels. If multiple labels are
used, then they must be connected with an AND operator. For example:
resource.labels.instance_id="1234567890" AND
resource.labels.zone="us-central1-a"
resource.labels.zone="us-central1-a" AND
metric.labels.instance_name="test_group" AND
metadata.user_labels.foo="bar" AND
metadata.system_labels.region="us-central1"
--criteria-policies=CRITERIA_POLICIES,[...]
The policies that the Snooze applies to. Exactly 1 alert policy is