Run timeline
What happened during a run and how it went: values over time with the events marked on them, the list of events, and the totals.
How it works
Connect a block's live telemetry (or a Telemetry block), and after the run its files too (a timeline CSV, an events JSON, a KPIs JSON). Values: the fields to draw over time, as channel.field=Label (for example kpi.orders_h=Orders per hour, kpi.backlog=Orders waiting); empty draws the first numbers of the stream.
Events: the channel whose items carry a text (and a kind); each one is a mark on the time line, coloured by kind, and a line in the list. Incidents and their clearing (events of kind incident and cleared with the same incident number) show as bands, with how long each took.
The tiles give the run's totals: duration, events, incidents and the time to clear them, and for each value its average, lowest and highest; a KPIs file adds its fields. Click an event to find it on the time line; drag across the chart to zoom, double-click to zoom out. Save events writes them as CSV.
Inputs
| Input | Takes | What it is |
|---|---|---|
Datadata | Stream or Table or Metrics or Items csv, json | Live telemetry with values and events, or the run's timeline, events and KPIs files Takes several connections. |
Settings
| Setting | Default | What it does |
|---|---|---|
Values over timevalues |
empty | channel.field=Label, separated by commas; :% or :time after a label formats it |
Events channelevents_channel |
event | |
Totals from a KPIs filetotals |
empty | field=Label, separated by commas; empty shows its numbers |
Titletitle |
empty |
Where it runs
In the browser, on the flow's View page and in the run's results, in a sandbox without network access. It needs no worker.