media server logo
Produkt-Benutzerhandbuch

Dashboard-Übersicht

Read the live state of the instance, arrange the widgets you use, and move directly to the module that needs attention.

In Callaba findenDashboard
Was dieses Modul leistet

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

  1. 01

    Sign in and scan the header for CPU, memory, disk or process warnings.

  2. 02

    Keep the widgets for the live path you operate and remove visual noise from unrelated modules.

  3. 03

    Arrange the widgets from contribution to delivery, then open any resource whose state is unexpected.

Workflow-Beispiele

Geeignet für

Build an incident view

A live program depends on one SRT input, a recording and a browser player.

SRT statusContribution
RecordingArchive
Web playerAudience
Host healthCapacity
Animiertes Workflow-Diagramm: Build an incident view

So wird er aufgebaut

  1. 1

    Place SRT servers, Recordings, Web players and host health in the first visible row.

  2. 2

    Confirm that the source and downstream resources are active.

  3. 3

    Open the first widget whose state differs from the expected live 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.
Dann so vorgehen

Create or restore the underlying resource; the dashboard does not invent placeholder data.