Get Service
cloud_monitoring.get_service
ActionGoogle Cloudconnection required
Calls monitoring v3 GET /v3/{parent}/services/{servicesId}.
Get the named Service.
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
2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
parent Parent resource: projects/ID, organizations/ID or folders/ID. Defaults to the connection's project. | string | No | — | — | — |
service Service name or id. | string | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
appEngine | object | — |
basicService | object | — |
cloudEndpoints | object | — |
cloudRun | object | — |
clusterIstio | object | — |
custom | object | — |
displayName | string | — |
gkeNamespace | object | — |
gkeService | object | — |
gkeWorkload | object | — |
istioCanonicalService | object | — |
meshIstio | object | — |
name | string | — |
telemetry | object | — |
userLabels | object | — |
{
"appEngine": {},
"basicService": {},
"cloudEndpoints": {},
"cloudRun": {},
"clusterIstio": {},
"custom": {},
"displayName": "",
"gkeNamespace": {},
"gkeService": {},
"gkeWorkload": {},
"istioCanonicalService": {},
"meshIstio": {},
"name": "",
"telemetry": {},
"userLabels": {}
}See Get Service 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.