mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-09 19:06:53 +00:00
93 lines
3.7 KiB
Text
93 lines
3.7 KiB
Text
NAME
|
|
gcloud alpha monitoring snoozes create - create a new snooze
|
|
|
|
SYNOPSIS
|
|
gcloud alpha monitoring snoozes create [--snooze-from-file=PATH_TO_FILE]
|
|
[--criteria-filter=CRITERIA_FILTER
|
|
--criteria-policies=CRITERIA_POLICIES,[...]
|
|
--display-name=DISPLAY_NAME
|
|
--end-time=END_TIME --start-time=START_TIME] [GCLOUD_WIDE_FLAG ...]
|
|
|
|
DESCRIPTION
|
|
(ALPHA) Creates a new snooze. A snooze can be specified as a JSON/YAML
|
|
value passed in as a file through the --snooze-from-file flag. A snooze can
|
|
also be specified through command line flags. If a snooze is specified
|
|
through --snooze-from-file, and additional flags are supplied, the flags
|
|
will override the snooze's settings.
|
|
|
|
For information about the JSON/YAML format of a snooze:
|
|
https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.snoozes
|
|
|
|
EXAMPLES
|
|
To create a snooze with command-line options, run:
|
|
|
|
$ gcloud alpha monitoring snoozes create \
|
|
--criteria-policies=LIST_OF_POLICIES --criteria-filter=FILTER \
|
|
--display-name=DISPLAY_NAME --start-time=START_TIME \
|
|
--end-time=END_TIME
|
|
|
|
To create a snooze with a file, run:
|
|
|
|
$ gcloud alpha monitoring snoozes create --snooze-from-file=MY-FILE
|
|
|
|
Sample contents of MY-FILE:
|
|
|
|
criteria:
|
|
policies:
|
|
- projects/MY-PROJECT/alertPolicies/MY-POLICY
|
|
filter: 'resource.labels.zone="us-central1-a" AND resource.labels.instance_id="1234567890"'
|
|
interval:
|
|
startTime: '2024-03-01T08:00:00Z'
|
|
endTime: '2024-03-08T04:59:59.500Z'
|
|
displayName: New Snooze
|
|
|
|
FLAGS
|
|
--snooze-from-file=PATH_TO_FILE
|
|
The path to a JSON or YAML file containing the snooze. Use a full or
|
|
relative path to a local file containing the value of snooze.
|
|
|
|
Snooze Settings. If any of these are specified, they will overwrite fields
|
|
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:
|
|
resource.labels.instance_id="1234567890" AND
|
|
resource.labels.zone="us-central1-a"
|
|
|
|
--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.
|
|
|
|
--end-time=END_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,
|
|
--billing-project, --configuration, --flags-file, --flatten, --format,
|
|
--help, --impersonate-service-account, --log-http, --project, --quiet,
|
|
--trace-token, --user-output-enabled, --verbosity.
|
|
|
|
Run $ gcloud help for details.
|
|
|
|
NOTES
|
|
This command is currently in alpha and might change without notice. If this
|
|
command fails with API permission errors despite specifying the correct
|
|
project, you might be trying to access an API with an invitation-only early
|
|
access allowlist. These variants are also available:
|
|
|
|
$ gcloud monitoring snoozes create
|
|
|
|
$ gcloud beta monitoring snoozes create
|
|
|