media server logo
Hướng dẫn sản phẩm

Tình trạng hệ thống và chẩn đoán

Interpret CPU, memory, disk, process and SRT error signals, test capacity, and preserve evidence before clearing incident logs.

Vị trí trong CallabaDashboard header → Instance health
Mô-đun này làm gì

Health signals explain whether the host can sustain the media workflow. Use them with module statistics: a healthy host does not prove a source is live, and a live source does not prove the host has headroom.

Trước khi bắt đầu

  • A known normal baseline for this instance and workload.

  • Permission to inspect or clear operational error logs.

  • An external incident record before destructive cleanup.

Giải thích cài đặt

Chỉ các điều khiển cần thiết cho vận hành viên được giải thích; tên trường nội bộ và sự kiện triển khai được chủ động ẩn.

Capacity

Read current host headroom.

CPU usage

Current processing load across media and application work.

Memory usage

Current RAM pressure.

Disk usage

Space available for logs, uploads, temporary transcoding and recordings.

Network speed test

Measured network capacity from the instance.

Run outside critical production peaks.

Operational evidence

Identify failures before changing configuration.

Process errors

Application/media process failures requiring module-level investigation.

SRT errors

SRT transport events and errors associated with contribution workflows.

Version notification

Installed application version and update context.

Clear error logs

Remove accumulated error entries.

Export or record incident evidence first.
IP location

Resolve regional context for a connection address when supported.

Luồng đầu tiên an toàn

  1. 01

    Compare CPU, memory and disk with the known healthy baseline.

  2. 02

    Open process or SRT errors and identify the owning module and time window.

  3. 03

    Inspect that module's live statistics and real input/output.

  4. 04

    Run a speed test only when it will not distort production traffic.

  5. 05

    Record or export incident evidence before clearing logs.

Ví dụ luồng công việc

Dùng khi

Diagnose unstable live transcoding

Output frames drop after a new transcoding job starts.

Live sourceInput bitrate
TranscodingCodec workload
Host healthCPU + memory
OutputFPS + bitrate
Sơ đồ luồng có chuyển động: Diagnose unstable live transcoding

Cách xây dựng

  1. 1

    Confirm the source bitrate is stable.

  2. 2

    Compare host CPU/memory before and after the job starts.

  3. 3

    Inspect output bitrate and frame rate.

  4. 4

    Remove unnecessary resize/frame-rate/codec work or move to measured host capacity.

Dùng khi

Preserve evidence before clearing errors

Old errors obscure an active incident investigation.

Error listTime + module
Incident recordPreserve evidence
Clear logsControlled action
ReproduceFresh signal
Sơ đồ luồng có chuyển động: Preserve evidence before clearing errors

Cách xây dựng

  1. 1

    Record the relevant error, timestamp, module and current release version.

  2. 2

    Save the associated module configuration and live statistics.

  3. 3

    Clear errors only after the evidence is externalized.

  4. 4

    Reproduce one controlled test and investigate only the new entries.

Xác minh kết quả

  • Capacity values match the expected workload and leave planned headroom.
  • Every active error can be tied to a time and owning module.
  • Clearing logs occurs only after evidence is stored elsewhere.

Khắc phục sự cố

Host health is normal but playback fails

Kiểm tra
  • Inspect the source and output modules.
  • Check access, protocol and real client playback.
Sau đó thực hiện

Treat host health as one layer; repair the first failed media boundary.