Dashboard Utils (dashboard-tools)
The dashboard-utils runner image implements the dashboard-tools feature: JMESPath filtering, legacy and Next dashboard aggregation, upload gates, and pipeline-specific transforms. Public docs use the URL path /runners/dashboard-tools/; the container image name is dashboard-utils.
Node template selection
| Template | Purpose | Limitations | Details |
|---|---|---|---|
dashboard-v2 | Publish a Next dashboard dimension from $heat-dataservice plus v2 layoutConfiguration. | Requires normalizable $heat-dataservice; 50-realm soft cap; not for ui/legacy. | dashboard-v2 · contract |
dashboard | Publish a Legacy v1 dimension from facade-style JSON keys. | Fixed v1 keys; do not use for new Next work. | dashboard |
json-filter | Extract a JSON subset with JMESPath before aggregation. | JSON only, single parent. | json-filter |
session-metadata-enrich | Copy small KPI fields into session metadata. | Object only, ≤ 20KB, no arrays. | session-metadata-enrich |
ecs-transform | Map ECS event JSON to legacy dashboard fragments. | ECS-specific; v1 shapes only. | ecs-transform |
opendis-parser | Parse OpenDIS PDU byte streams to JSON. | DIS binary input required. | opendis-parser |
lattice-processor | Summarize mixed binary uploads (archives, formats). | Report only; not a dashboard publisher. | lattice-processor |
filter-payload | Gate uploads by allowedTypes. | Type gate only. | filter-payload |
filter-node | Validate type and optional schema after filter-payload. | Parent must be named filter-payload. | filter-node |
session-trigger | Reprocess a target-node for sessions matching metadata. | Operational side effect. | session-trigger |
Typical pipelines
Next (recommended):
Legacy v1:
Ingest gate: