Monitoring

Introduction

SpinetiX players are designed to run continuously and reliably - the time spent on maintenance will be insignificant. Nevertheless, there are moments, depending on different factors, when the player might not be running properly or running in a reduced-functionality state.

• If the player gets stuck rendering content for 60 seconds, then it will automatically reboot. If this happens three times in quick succession, then the player will enter Safe mode, allowing you to query the logs to find the content / resource that is causing this.
• If the problem is more serious (storage / firmware corruption, hardware issue etc.), the player will enter into Recovery mode.
• It is extremely rare for the player to freeze and require manual intervention.

Methods

For those special cases, the health of your players can be monitored via the network in different ways:

• Cockpit can be used to monitor any number of SpinetiX players, using either Basic or Premium monitoring service for each player.
• RPC API is the recommended method for complex monitoring since it allows for direct or indirect commands to be sent to the player to get the player status as response, to remotely trigger a firmware update or to reboot the player. RPC can also be used to listen for the notifications sent by the HMP, like "Ready" (the heartbeat) or "Restart". Check out the RPC Server-side application samples as examples of RPC based monitoring using PHP.
• Status API to get the up-time, temperature, device stats, snapshot etc.
• SNMP monitoring and / or ICMP ping utility can be used to monitor up-time.
• Elementi's Devices view can be used to monitor the HMP devices from the LAN - click on the "Devices" tab in Browse panel to get an overview of the HMP statuses - you can easily spot the ones having problems by the device icon. For HMD, see HMD devices (GUI) page.