imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-20 21:20:07 +00:00
Code Activity

gcloud: Wed Feb 11 11:28:24 UTC 2026

Browse source
This commit is contained in:
Automated 2026-02-11 11:28:25 +00:00
parent 582f364023
commit aaff695a08
2667 changed files with 84754 additions and 68242 deletions
Download patch file Download diff file Expand all files Collapse all files

48
gcloud/monitoring/snoozes/create
View file

@ -49,34 +49,34 @@ FLAGS
Snooze Settings. If any of these are specified, they will overwrite fields
in the --snooze-from-file flags if specified.
--criteria-filter=CRITERIA_FILTER
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" AND
metric.labels.instance_name="test_group" AND
metadata.user_labels.foo="bar" AND
metadata.system_labels.region="us-central1"
--criteria-filter=CRITERIA_FILTER
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" 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
required if criteria-filter is specified at the same time.
--criteria-policies=CRITERIA_POLICIES,[...]
The policies that the Snooze applies to. Exactly 1 alert policy is
required if criteria-filter is specified at the same time.
--display-name=DISPLAY_NAME
The display name for the Snooze.
--display-name=DISPLAY_NAME
The display name for the Snooze.
--end-time=END_TIME
The end time for the Snooze.
--end-time=END_TIME
The end time for the Snooze.
--start-time=START_TIME
The start time for the Snooze.
--start-time=START_TIME
The start time for the Snooze.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

6
gcloud/monitoring/snoozes/update
View file

@ -75,8 +75,10 @@ FLAGS
The list of fields to update. Must specify --snooze-from-file if
using this flag.
Snooze Settings. If any of these are specified, they will overwrite
fields in the --snooze-from-file flags if specified.
Or at least one of these can be specified:
Snooze Settings. If any of these are specified, they will overwrite
fields in the --snooze-from-file flags if specified.
--display-name=DISPLAY_NAME
The display name for the Snooze.