Update Snooze

cloud_monitoring.update_snooze
ActionGoogle Cloudconnection required

Calls monitoring v3 PATCH /v3/projects/{projectsId}/snoozes/{snoozesId}.

Updates a Snooze, identified by its name, with the parameters in the given Snooze object.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Cloud Monitoring
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
snooze
Snooze name or id.
stringYes———
body
The Snooze resource, as the API defines it.
objectYes———
update_mask
The fields to update.For each field listed in update_mask: If the Snooze object supplied in the UpdateSnoozeRequest has a value for that field, the value of… Optional.
stringNo———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
criteria
object—
displayName
string—
interval
object—
name
string—
{
  "criteria": {},
  "displayName": "",
  "interval": {},
  "name": ""
}

See Update Snooze run in a workflow.

In a technical demo we add the Google Cloud Monitoring connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.