Update Service Level Objective

cloud_monitoring.update_service_level_objective
ActionGoogle Cloudconnection required

Calls monitoring v3 PATCH /v3/{parent}/services/{servicesId}/serviceLevelObjectives/{serviceLevelObjectivesId}.

Update the given ServiceLevelObjective.

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

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

FieldTypeRequiredDefaultConstraintsExample
parent
Parent resource: projects/ID, organizations/ID or folders/ID. Defaults to the connection's project.
stringNo———
service
Service name or id.
stringYes———
service_level_objective
Service level objective name or id.
stringYes———
body
The ServiceLevelObjective resource, as the API defines it.
objectYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
calendarPeriod
string—
displayName
string—
goal
number—
name
string—
rollingPeriod
string—
serviceLevelIndicator
object—
userLabels
object—
{
  "calendarPeriod": "",
  "displayName": "",
  "goal": 0,
  "name": "",
  "rollingPeriod": "",
  "serviceLevelIndicator": {},
  "userLabels": {}
}

See Update Service Level Objective 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.