Player monitoring in Cockpit

From SpinetiX Support Wiki

Jump to: navigation, search

Introduction

Player Monitoring service offers to Cockpit users the possibility to monitor any number of SpinetiX players, using either Basic or Premium monitoring service for each player.

Any new player benefits from a free 30-day Premium monitoring when registered in Cockpit for the first time.


Note Note: See how to add and remove players from Cockpit.

Basic monitoring service

The basic player monitoring is a free service that offers access to standard player information from anywhere, at anytime. It can be used for unlimited time and unlimited number of players.

Its main benefits are:

  • Overview of current player statuses.
  • Monitoring of all important information (firmware version, snapshots, locations) useful for quick support and maintenance.
  • Compatible with all players (DiVA and HMPs; new and already deployed players).

The basic monitoring service has a lower update rate, comparing to premium monitoring service, but no less than once per day. Thus it is not suitable for real-time monitoring.

Premium monitoring service

The premium player monitoring is a paid service that offers access to advanced monitoring and notification tools with high monitoring precision. It has the following additional features compared to basic player monitoring:

  • Automatic SMS and / or email notification alerts to react promptly in case of issues.
  • Player risks scenarios through automatic detection of major failure and potential risks scenarios.
  • Player history for all players for accurate performance statistics and advanced diagnostics.
  • Faster and easier access to SpinetiX distributor support.

These extra features allow you to reduce your support costs and to increase your support quality.

Monitoring tools

The following monitoring tools can be used once a player has been added in Cockpit.

  • Map summary
  • Table summary
  • Player Dashboard (Premium only)
    Clicking on a specific player gives the user access to the detailed status of a player.
    • Health trackers (Temperature, Storage, CPU usage, Up-time, ...)
    • Timeline (list of status and events)
    • Player snapshot
  • Notification (Premium only)

The following left menu items are available when clicking on a player:

  • Dashboard: monitor the player
  • Setup: configure the player GPS information and delete the player from cockpit.
  • Licenses (dealer only): manage the player Premium licenses
  • Events: configure the events to be monitored and the player monitoring time and days
  • User Access: give access to the player to other users (Viewers of Distributors for instance)

Map summary

Map summary

The map summary is accessible to all users from the page Cockpit.

All players belonging to the user are shown on the map. When multiple players are on the same location, a blue circle with the amount of player is shown. Clicking on the circle will zoom the map on the all the player in this area.

The color of the player pin indicates the status of the player.

  • Green: OK
  • Orange: Warning, may be one of the following: no connected screens, screen turned off,...
  • red: Failure, may be one of the following: Corrupted firmware, player in Safe mode,...
  • Grey: Off-line

When clicking on a player a summary pop-up is shown with:

  • Player name
  • Player serial number
  • HMP model
  • Firmware version
  • Time of the last status update.
  • Snapshot of the player content.

Another click on the pop-up will open the player dashboard.

Players summary

Players summary

The player summary is accessible to all users from the page Players.

All player belonging to the user are shown in the list. The list can be search using the text entry on the top-right of the page.

For each player the following information is shown.

  • Status of the player indicated by the color of the the row.
  • Type of license (trial, freemium or empty for premium)
  • Events traffic lights, indicating events that have occurred since the last time the dashboard was opened.
  • Player name
  • Player serial number
  • HMP model
  • Firmware version
  • Time of the last status update.
  • Snapshot of the player content.

Clicking on a player will open the player dashboard.

Player Dashboard

Player dashboard

The player dashboard is only accessible for players using Premium monitoring licenses.

The player dashboard is composed of three main elements:

  • Health trackers
    The health tracker indicated the current state of the player. It can be used to get a quick indication of the current player status.
  • Timeline
    The timeline represent the history of the player. Status changes and events are show in chronological order.
  • Content snapshot

What can be monitored

Monitoring off-line status

Off-line status

Player on-line and off-line status is the base of the monitoring offered by Cockpit.

If the player fails to communicated with Cockpit at regular intervals, it is considered as being offline. The last status of the player (OK, warning, or failure) is kept, but the color is switched to gray to indicated that no further information is being received by the player.

An offline player status can indicate one of the following:

  • Player is no longer running;
  • Network is down;
  • Proxy server, if any, is blocking the player access to Cockpit;
  • Player has rebooted in Recovery mode;


Note Note: Off-line status monitoring can be turned off using the Events page of the player.

Monitoring screens

Screen status

Cockpit monitors the status of the screen connected to the player. The monitoring of the screen itself is done by the HMP using Display Data Channel (DDC).

Screen status may be one of the following:

  • ok: the screen is connected and powered
  • off: the screen is connected but powered off.
    This events is a warning and will put the player is warning status.
  • No screen attached: the screen is not connected.
    This events is a warning and will put the player is warning status.

Notes:

  • not all the screens are reporting their on/off status. In this case Cockpit may just indicated that the screen is ok, when the screen is connected to the player.
  • Some VGA monitor and cable do not support Display Data Channel (DDC). In such case the screen may be reported as not attached by Cockpit.
  • Screen monitoring can be turned off using the Events page of the player.

Monitoring storage

Storage status

Cockpit monitors the internal storage space available in the player.

Storage status may be one of the following:

  • Storage ok
  • Storage almost full (85%)
    This events is a warning
  • Storage full (95%)
    This events is a warning

Notes:

  • Storage monitoring can be turned off using the Events page of the player.

Monitoring content

Content status
Safe mode detection

Cockpit monitors the content player by the HMP, and issue that may be raised by it.

The Load average health tracker may indicated content that are not rendered correctly by the player. Load above 80% should be considered as potentially problematic. Additionally, reboot of the player because of content freeze are a good indication of over-demanding content.

In case of content failure, the player may end up in Safe mode. This will put the player in Failure state.

Typical events indicating issue with the content.

  • Player restarted: Content freeze
    This events is a warning
  • Player restarted: Content failure
    This events is a warning
  • Player in safe mode
    This events is a failure and will put the player in failure state.
  • Player restarted: Timeout
    This events is a failure as the player was left one hour in safe mode without user actions.

Monitoring uptime/power

Uptime status
Power loss

Cockpit monitors up-time of the player and various reason for reboots.

The up-time health tracker indicates how long the player has been working without reboots. User triggered reboots (using Control Center, the Blue button or RPC) are shown in the timeline.

Restarts due to power failure are considered as warning events, and may indicated issues with the power source or the environment of the player.

Monitoring temperature

Temperature status

Cockpit monitors the internal temperature of the player. The current temperature with a 5 hours history is displayed as part of the health trackers.

The following events are monitored by Cockpit

  • Temperature ok
  • Temperature high
    This events is a warning. It is raised when the internal temperature is above 60°C (140°F).
  • Player restarted: Critical temperature exceeded
    This events is a failure

Notes:

  • Temperature monitoring can be turned off using the Events page of the player.

Monitoring firmware

Firmware status

Cockpit monitors the firmware version of the HMP. The following events are monitored by Cockpit

  • Firmware version upgraded
  • Firmware version downgraded
  • Player restarted: Firmware updated

Notes:

  • User can be notified when firmware version of players is modified.

Setup

Setup players

The setup page let the user configure the player information and delete the player from cockpit.

In addition to the player name the user may configure

  • Notes
    Free form notes to indicate extra information for this player
  • Contact
    Free form contact information for this player in case of need.
  • Address
    Localization of the player. If the address is filled up, Cockpit will try to automatically find the GPS coordinate and position the player on the map.
  • GPS coordinates
    Cockpit will use automatic GPS localization of the player based on its IP address. You can correct this position either using the address, or directly by moving the player on the map.

Events

Configuring events

The Events page let you configure the the events to be monitored and the player monitoring times and days.

The following category of events can be configured:

  • Connectivity
    If unchecked the player will not be detected as off-line and no notifications of off-line, on-line status will be sent.
  • Screen
    If unchecked the screen status will not be monitored by cockpit
  • Storage
    If unchecked no storage warning will be present in the timeline, storage health box will still be displayed and populated
  • Temperature
    If unchecked no temperature warning will be present in the timeline, temperature health box will still be displayed and populated.
    Note that this will not present player reboots events if the temperature exceed the maximum thresholds.

Alerts

Configuring alerts

The Alerts page, available from the top right user menu, let you configure the the alerts to be sent by email or by SMS.

You can enter any number of emails and SMS to be notified, the same emails/SMS will be used for all notifications.

The following state notifications can be sent:

  • Success
    Notification is sent if a player was in warning or error state and returns to normal (OK) state
  • Warning
    Notification is sent when a player state changes to warning, regardless of the reason for the state change.
  • Failure
    Notification is sent when a player state changes to failure, regardless of the reason for the state change.

The following event notifications can be sent:

  • Connectivity lost
    Notification is sent if a player goes off-line and the connectivity events are monitored.
  • Connectivity restored
    Notification is sent if an off-line player goes back on-line and the connectivity events are monitored.
  • Firmware version changed
    Notification is sent if the firmware version of the player is modified.
  • License warnings and errors
    Notification is sent if a player premium license expires.
  • Screen changes
    Notification is sent if the screen status is modified and the screen events are monitored.
  • Storage warnings
    Notification is sent if storage warnings occurs and the storage events are monitored.
  • Temperature warnings
    Notification is sent if temperature warning occurs and the temperature events are monitored.
  • Other warnings
    Notification is sent if a warning event (not in the list above) occurs, such as:
    • Reboot because of power cut;
    • Reboot because of content crash;
    • Reboot because of content not being rendered in 30s / 60s;
    • Player connecting to Cockpit with wrong identifications;
    • Player already bounded in Cockpit added to another account.
  • Other failures
    Notification is sent if a failure events (not in the list above) occurs, such as:
    • Player in safe mode;
    • Publish/Upload error;
    • Reboot because of too high temperature;
    • Reboot because the HMP was left 1h in safe mode.
This page was last modified on 16 September 2016, at 18:05. This page has been accessed 3,212 times.