Live Data
Live Data captures pipeline messages at configurable processing stages, enabling real-time observation of data as it flows through the telemetry pipeline. Use it to verify data transformations, diagnose routing issues, and inspect message content at specific points in the processing chain.
Availability
Live Data is available from the detail pages of the following components:
| Component | Navigation Path |
|---|---|
| Director | |
| Cluster | |
| Device | |
| Target | |
| Advanced Route |
The Pipeline Debugger also supports Live Data as a dataset provider, allowing you to capture live pipeline messages for use as debug input.
Using Live Data
The Live Data panel follows the same control pattern as Console Logs:
- Configure capture parameters using the
Filter button — select a capture location and set time/count limits - Optionally enter text in the query input field to restrict output to messages containing it — the field is disabled while a capture is running, so set it before starting
- Click
Capture to begin streaming - Messages appear in the output area as they are captured
- Click
Stop to end capture, or wait for the capture time to elapse - Click the
Copy button to copy captured output to the clipboard — available only once capture has stopped and at least one message was received - Click
Clean to clear the output and reset to idle state
Capture stops automatically when either the capture time or the capture count limit is reached, whichever occurs first.
Filter Options
Click the
| Option | Type | Range | Default | Description |
|---|---|---|---|---|
| Choose where to capture | Dropdown | Context-dependent | See below | Pipeline stage at which to capture data |
| Capture time in seconds | Number | 5–60 | 10 | Maximum duration of the capture session |
| Capture up to N events | Number | 100–5,000 | 1,000 | Maximum number of messages to capture |
Click
Capture Locations
The capture location determines at which pipeline stage messages are intercepted. Available locations depend on the component context.
Director, Cluster, Device, and Target
| Location | Description |
|---|---|
| Before pre-processing | Raw data as received, before any pre-processing pipeline executes |
| After pre-processing | Data after pre-processing pipeline execution |
| Before post-processing | Data before post-processing pipeline executes |
| After post-processing | Final data after all post-processing, as delivered to the target |
The default selection depends on the component: Before post-processing for Directors and Clusters, Before pre-processing for Devices, and After post-processing for Targets.
Advanced Route
| Location | Description |
|---|---|
| Before route | Data as it enters the route, before route processing (default) |
| After route | Data after route processing completes |
Source Filtering
The component context determines which data is visible during capture:
- Director — Captures all data flowing through the Director instance across all devices, targets, and routes
- Cluster — Captures all data flowing through the Cluster
- Device — Captures only data originating from that specific device
- Target — Captures only data destined for that specific target
- Advanced Route — Captures only data flowing through that specific route
Prerequisites
Live Data requires the component to be enabled and have an active data path. When conditions are not met, the panel displays a context-specific alert:
| Component | Enabled Condition | Connected Condition |
|---|---|---|
| Director | Director must be enabled | Director must be connected |
| Cluster | Cluster must be enabled | Cluster must be connected |
| Device | Device must be enabled | At least one associated Director must be connected |
| Target | Target must be enabled | At least one route must be sending data to the target |
| Advanced Route | Route must be enabled | At least one associated Director must be connected |