Put Metric
cloudwatch.put_metric_data
ActionAmazon Web Servicesconnection required
Calls the AWS cloudwatch API (SigV4).
Publish a custom metric datapoint.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Amazon CloudWatch
- Secret shape
- {"access_key_id", "secret_access_key"}
- Config it needs
- region
- Resolved by
- config.connection_id, else node.connection_id
Configuration
6 fields, 3 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 |
|---|---|---|---|---|---|
region AWS region (overrides the connection). | string | No | — | — | — |
namespace Metric namespace. | string | Yes | — | — | — |
metric_name Name of the metric to act on, from cloudwatch.list_metrics. | string | Yes | — | — | — |
value Datapoint value. | number | Yes | — | — | — |
unit Count | Seconds | Bytes | …. | string | No | — | — | — |
dimensions {"InstanceId": "i-1"} | object | No | — | — | {"InstanceId":"i-1"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"dimensions": {
"InstanceId": "i-1"
}
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
namespace | string | — |
metric_name | string | — |
{
"metric_name": "",
"namespace": "",
"ok": false
}Related Amazon CloudWatch nodes
Solutions with Amazon CloudWatch
See Put Metric run in a workflow.
In a technical demo we add the Amazon CloudWatch connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.