Metrics

Node catalog Actions

On this page

Publish business measurements without changing workflow data.

Usage and specifics

Declare metrics and map their values from run data. Check types and results in execution metrics before using them in a dashboard.

Technical type : metrics. Runtime : nodulz.

Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the credentials guide if a remote source or execution target requires access.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`declarations`	`array`	`[]`	-; max 20
`declarations[].id`	`string`	-	-; min 1, max 100
`declarations[].name`	`string`	-	-
`declarations[].description`	`string`	`""`	-; max 512
`declarations[].unit`	`enum`	`""`	``, `seconds`, `bytes`, `ratio`
`declarations[].type`	`enum`	`"gauge"`	`gauge`, `counter`, `histogram`
`declarations[].value`	`union`	`1`	-
`declarations[].labels`	`array`	`[]`	-; max 8
`declarations[].labels[].name`	`string`	-	-
`declarations[].labels[].value`	`string`	-	-; max 1024
`declarations[].buckets`	`array`	`[0.1,0.5,1,5,10,30,60]`	-; min 1, max 20
`declarations[].when`	`enum`	`"success"`	`success`, `failed`, `always`

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "declarations": []
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.