Topic 1 of 5

#Use the Dashboard as a starting point

Click-by-clickThe 60-second dashboard check
Dashboard
  1. 1
    Config loaded

    This should be healthy. If it is not, stop and report it.

  2. 2
    Serving enabled

    This should be healthy. If it is disabled unexpectedly, stop and report it.

  3. 3
    Players

    Look for a count that is different from the normal shift or venue schedule.

  4. 4
    System warnings

    Read the exact warning. The words matter more than the colour.

  5. 5
    Disk usage

    Check for a low-space warning before uploading or releasing large content.

You are finished when you know whether the platform looks normal and which one workspace to open next.

Dashboard cards point to a problem; they do not fix it.

The Dashboard is a summary, not the final diagnosis. Use it to decide where to look next, then open the relevant player, job or presentation for detail.

BrightBridge Dashboard health overview showing player, deployment, serving, system, uptime, warnings and disk usage cards
Read left to right: fleet size first, then deployment and serving health, then host load, warnings and storage. The values shown are an example captured from the live interface and will change.
Topic 2 of 5

#Fleet cards

CardWhat to check
Total playersWhether the visible fleet size is expected
Online or recentPlayers with fresh activity
OverduePlayers that have not reported within the expected window
OfflinePlayers needing schedule context or investigation
UnknownPlayers without enough activity information
Topic 3 of 5

#Recent activity and jobs

  • Open failed or partial work before starting another fleet-wide action.
  • A completed release still needs player-side verification.
  • Repeated warnings on the same player usually deserve targeted investigation.
  • Use timestamps to distinguish a current incident from old history.
Topic 4 of 5

#Storage indicators

Low available storage can interrupt uploads, content preparation or backups. If the Dashboard shows a storage warning, pause large content changes and ask an authorised maintainer to review retained material.

Topic 5 of 5

#Choose the next action

ObservationNext workspace
Unexpected offline playerPlayers → player detail
Failed content releaseDeployment → job result
Presentation upload problemPresentation library
Poor connection testUtility Tools
Several screens need visual checkingMultiview