Resource: Snooze
A Snooze
will prevent any alerts from being opened, and close any that are already open. The Snooze
will work on alerts that match the criteria defined in the Snooze
. The Snooze
will be active from interval.start_time
through interval.end_time
.
JSON representation |
---|
{ "name": string, "criteria": { object ( |
Fields | |
---|---|
name |
Required. Identifier. The name of the
The ID of the |
criteria |
Required. This defines the criteria for applying the |
interval |
Required. The |
display |
Required. A display name for the |
Criteria
Criteria specific to the AlertPolicy
s that this Snooze
applies to. The Snooze
will suppress alerts that come from one of the AlertPolicy
s whose names are supplied.
JSON representation |
---|
{ "policies": [ string ] } |
Fields | |
---|---|
policies[] |
The specific
There is a limit of 16 policies per snooze. This limit is checked during snooze creation. |
TimeInterval
Describes a time interval:
- Reads: A half-open time interval. It includes the end time but excludes the start time:
(startTime, endTime]
. The start time must be specified, must be earlier than the end time, and should be no older than the data retention period for the metric. - Writes: A closed time interval. It extends from the start time to the end time, and includes both:
[startTime, endTime]
. Valid time intervals depend on theMetricKind
of the metric value. The end time must not be earlier than the start time, and the end time must not be more than 25 hours in the past or more than five minutes in the future.- For
GAUGE
metrics, thestartTime
value is technically optional; if no value is specified, the start time defaults to the value of the end time, and the interval represents a single point in time. If both start and end times are specified, they must be identical. Such an interval is valid only forGAUGE
metrics, which are point-in-time measurements. The end time of a new interval must be at least a millisecond after the end time of the previous interval. - For
DELTA
metrics, the start time and end time must specify a non-zero interval, with subsequent points specifying contiguous and non-overlapping intervals. ForDELTA
metrics, the start time of the next interval must be at least a millisecond after the end time of the previous interval. - For
CUMULATIVE
metrics, the start time and end time must specify a non-zero interval, with subsequent points specifying the same start time and increasing end times, until an event resets the cumulative value to zero and sets a new start time for the following points. The new start time must be at least a millisecond after the end time of the previous interval. - The start time of a new interval must be at least a millisecond after the end time of the previous interval because intervals are closed. If the start time of a new interval is the same as the end time of the previous interval, then data written at the new start time could overwrite data written at the previous end time.
- For
JSON representation |
---|
{ "endTime": string, "startTime": string } |
Fields | |
---|---|
end |
Required. The end of the time interval. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
start |
Optional. The beginning of the time interval. The default value for the start time is the end time. The start time must not be later than the end time. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
Methods |
|
---|---|
|
Creates a Snooze that will prevent alerts, which match the provided criteria, from being opened. |
|
Retrieves a Snooze by name . |
|
Lists the Snooze s associated with a project. |
|
Updates a Snooze , identified by its name , with the parameters in the given Snooze object. |