Trends, recording & replay
Time series, evidence capture, export, and offline replay.
Trends, recording & replay
A Trend subscribes to numeric or Boolean values produced by source views. It does not create its own polling loop. Its floating bar reports how many required sources are running and can start missing sources from the Trend.
| Action | What it changes | What it preserves |
|---|---|---|
| Clear series | Removes collected chart samples | Configured series stay attached |
| Export | Writes the selected visible window | CSV, TSV, XLSX, JSON, or JSON Lines |
| Record | Captures new samples into a bounded session | Independent of React rendering |
| Replay | Opens a saved Trend or Raw Traffic session | No project, device, or connection required |
Create a useful Trend
Choose a question
Prefer a small set of signals that explain one behavior, such as setpoint, measured value, enable, and alarm.
Attach series
Add numeric or Boolean tags from source views. Existing saved Trends are edited in Project Settings to keep viewing and configuration separate.
Start missing sources
Use the floating bar. The source counter makes incomplete acquisition explicit.
Set the time window
Use a window that shows the process dynamics without compressing meaningful transitions.
Record before reproducing
If the event matters, start a bounded recording before triggering it. Exporting afterward only sees retained history.
Replay semantics
A replay tab is explicitly labeled Replay and owns an immutable local timeline. Scrubbing or changing playback speed never writes a project or sends traffic. Raw Traffic replay keeps the ordinary filters and frame inspector; Trend replay reconstructs chart samples and capture completeness, including dropped-count warnings.