Skip to content
ELYRA

Automation: console, network and performance

Commands that record the tab's console and network, detail a request, and record a performance trace.

View Markdown

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 capture start
elyra capture stop
elyra console [--limit <n>]
elyra network [--limit <n>]

console and network only return what was recorded with capture on. Without capture start, the lists come back empty — and an empty list looks like a silent page, not like a page without capture.

Correct flow:

  1. elyra capture start
  2. Reproduce the action you want to observe.
  3. elyra console and/or elyra network
  4. elyra capture stop

Detail a request

elyra network show --request <id>
  • The --request comes from elyra 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 performance trace start [--reload] [--categories <a,b>]
elyra performance trace stop [--out <path>]
  • start turns recording on; --reload reloads the page before starting, and --categories restricts the categories.
  • Only one trace per tab: starting twice is refused.
  • stop saves 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.
  1. capture start
  2. Reproduce the problem.
  3. network — see what failed.
  4. network show --request <id> — detail the suspect request.
  5. console — see the errors on the page side.
  6. capture stop

To measure performance, use performance trace instead of capture: the capture is of console and network, not of time.