The dashboard is an operator console, not a report page. It brings the status of SRT, RTMP, routes, recordings, restreams, web players, NDI adapters and active ports into one saved workspace.
Vor dem Start
A Callaba account with access to the instance.
At least one configured media module if you want its widget to show live resources.
Einstellungen erklärt
Hier werden die für Operatoren relevanten Bedienelemente erklärt. Interne Feldnamen und Implementierungsereignisse bleiben bewusst verborgen.
Workspace
Choose which operational signals remain visible after sign-in.
- Visible widgets
Show only the module summaries needed by the current operator role.
Keep ingest, output and host-health signals together for incident work.- Widget order
Drag widgets into the sequence in which your team checks a live workflow.
The order is saved for the dashboard user.
Live status
Each widget is a doorway into its owning module.
- Resource state
See whether configured resources are active before opening their full list.
- Module shortcut
Open the owning SRT, RTMP, route, recording, restream, player, NDI or port list from its widget.
Sicherer erster Workflow
- 01
Sign in and scan the header for CPU, memory, disk or process warnings.
- 02
Keep the widgets for the live path you operate and remove visual noise from unrelated modules.
- 03
Arrange the widgets from contribution to delivery, then open any resource whose state is unexpected.
Workflow-Beispiele
Build an incident view
A live program depends on one SRT input, a recording and a browser player.
So wird er aufgebaut
- 1
Place SRT servers, Recordings, Web players and host health in the first visible row.
- 2
Confirm that the source and downstream resources are active.
- 3
Open the first widget whose state differs from the expected live path.
Run a live-event readiness pass
Operators need one preflight surface for the primary feed, recovery path, recording and audience output.
So wird er aufgebaut
- 1
Arrange the source, recovery, recording and player widgets in the order the event team will check them.
- 2
Open each widget and confirm that its configured resource is active or ready for the planned start.
- 3
Verify a real preview and the recording destination before declaring the workflow ready.
- 4
Keep this dashboard layout during the event so every operator starts from the same path.
Ergebnis prüfen
- The selected widgets remain in the chosen order after a reload.
- Each module shortcut opens the matching resource list.
- Header capacity and error indicators agree with the detailed health view.
Fehlerbehebung
A widget is empty
Prüfen- Confirm the module contains at least one resource.
- Open the module list and verify your account can read it.
Create or restore the underlying resource; the dashboard does not invent placeholder data.