Query Time Sery
cloud_monitoring.query_time_sery
ActionGoogle Cloudconnection required
Calls monitoring v3 POST /v3/projects/{projectsId}/timeSeries:query.
Queries time series by using Monitoring Query Language (MQL).
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
1 field, 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 |
|---|---|---|---|---|---|
body The QueryTimeSeriesRequest resource, as the API defines it. | object | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
nextPageToken | string | — |
partialErrors | array | — |
timeSeriesData | array | — |
timeSeriesDescriptor | object | — |
{
"nextPageToken": "",
"partialErrors": [],
"timeSeriesData": [],
"timeSeriesDescriptor": {}
}See Query Time Sery 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.