Overview
Live Inspect provides an interactive terminal user interface (TUI) for monitoring and debugging your pipelines. View live data samples as they flow through each topology node (sources, transforms, and sinks) with features like multi-tab navigation, search, and scrolling.Basic usage
Inspect live data from a running pipeline:Command options
Pipeline name or path to YAML configuration file
Comma-separated list of topology node keys to filter. Only shows data from the
specified nodes. Example:
-n source1,transform1Maximum number of records to keep in the TUI buffer. Older records are removed when this limit is reached.
Path to config file
TUI interface
The inspect command opens an interactive terminal interface with the following features:Multi-tab navigation
Data is organized into tabs by topology node. The All tab shows records from all nodes, while individual tabs show records from specific sources, transforms, or sinks. Tabs appear dynamically as data arrives from each node.| Key | Action |
|---|---|
Tab or → | Next tab |
Shift+Tab or ← | Previous tab |
1-9 | Jump to tab by number |
Scrolling
Navigate through records using keyboard or mouse:| Key | Action |
|---|---|
j or ↓ | Scroll down one line |
k or ↑ | Scroll up one line |
g or Home | Jump to top |
G or End | Jump to bottom |
Page Up/Down | Scroll by page |
| Mouse wheel | Scroll up/down |
Search
Search across all visible records with highlighted matches:| Key | Action |
|---|---|
/ | Start search |
Enter | Execute search |
n | Jump to next match |
N | Jump to previous match |
Esc | Clear search |
Pipeline definition
Pressd to toggle the pipeline definition view. On the All tab, this shows the complete pipeline YAML. On individual node tabs, it shows only that node’s configuration.
Additional shortcuts
| Key | Action |
|---|---|
w | Open pipeline in web dashboard |
q or Ctrl+C | Quit |
Filtering topology nodes
By default, Live Inspect shows data from all nodes in your pipeline. Filter to specific nodes using the-n flag:
Auto-reconnection
The TUI automatically reconnects when:- The pipeline is updated, paused, or resumed
- The connection is temporarily lost
- The pipeline is stopped and restarted
The TUI has a 30-minute connection timeout. If the pipeline remains unreachable for 30 minutes, the TUI automatically closes with a message suggesting you check the pipeline status.
Buffer management
The TUI maintains a buffer of recent records for scrolling and searching. By default, it keeps the last 10,000 records. Adjust this with the-b flag:
Example
Inspect a pipeline and filter to a specific transform:- Pipeline name and status in the header
- Tabs for each topology node receiving data
- Live records with JSON pretty-printing
- Status bar with last record time and keyboard shortcuts
Use cases
Debugging transform logic
Debugging transform logic
Use Live Inspect to verify that your SQL transforms are filtering and transforming data correctly. Switch between tabs to compare input and output of each transform.
Verifying data sources
Verifying data sources
Quickly verify that your sources are producing data in the expected format. Use search to find specific records or patterns.
Monitoring deployments
Monitoring deployments
After deploying with
goldsky turbo apply -i, the TUI opens automatically so you can verify data is flowing correctly.Troubleshooting
No data appearing
No data appearing
If you don’t see any data:
- Verify your pipeline is running:
goldsky turbo list - Check that data is flowing:
goldsky turbo logs my-pipeline - The TUI shows “Waiting for records…” until data arrives
- If the pipeline is starting, the TUI will auto-reconnect when it becomes active
Pipeline not found
Pipeline not found
If you see “Pipeline not found”, verify the pipeline name with
goldsky turbo list or check that your YAML file path is correct.