Automation: console, network and performance
Commands that record the tab's console and network, detail a request, and record a performance trace.
Commands, flags and values are literal — they are not translated. All of them accept the target flags --page/--node/--workspace; without a target, they act on the active tab of the current workspace.
Capture console and network
elyra browser capture startelyra browser capture stopelyra browser console [--limit <n>]elyra browser network [--limit <n>]
consoleandnetworkonly return what was recorded with capture on. Withoutcapture start, the lists come back empty — and an empty list looks like a silent page, not like a page without capture.
Correct flow:
elyra browser capture start- Reproduce the action you want to observe.
elyra browser consoleand/orelyra browser networkelyra browser capture stop
Detail a request
elyra browser network show --request <id>- The
--requestcomes fromelyra browser network --json. - Only entries marked as having detail available can be resolved. Synthetic identifiers are refused, with guidance on what to do.
- Bodies above 64 KB are truncated, and the result says so.
Performance trace
elyra browser performance trace start [--reload] [--categories <a,b>]elyra browser performance trace stop [--out <path>]startturns recording on;--reloadreloads the page before starting, and--categoriesrestricts the categories.- Only one trace per tab: starting twice is refused.
stopsaves the JSON and reports the event count and the captured duration. Without--out, it saves in the current directory and says where.- The output path is restricted to the current directory.
Recommended order for investigating a problem
capture start- Reproduce the problem.
network— see what failed.network show --request <id>— detail the suspect request.console— see the errors on the page side.capture stop
To measure performance, use performance trace instead of capture: the capture is of console and network, not of time.

