Display Alerts: design an API and reporting for a display to report interesting events/alerts

[dasgarner]

Surface alerts through the CMS when interesting events happen on the display, e.g.

• App start
• Power cycle
• Network disconnect/connect
• TV monitoring (power state and input source)

Each player app would be responsible for sending the things it can from a list of options.

This data should be recorded as a display event, meaning the following changes will need to be made to the data model:

• start columns should be nullable
• new columns for:
  • eventTypeId
  • refId
  • detail

Basic reporting should be made available to show these events (to be extended in future with more advanced reporting).

XMDS submitLog should be modified to process a log node with category=event and expect the additional fields when processing that record. The detail column would be the text content of the node. The XML structure should be documented and communicated to the player development teams and in the development docs.

There are notable transactions for which the CMS should also record events:

• A new fault added to the fault list, and then being cleared (via the refId)
• All faults cleared

Finally we should have the option of storing display events in MongoDB as well as MySQL, including migrating old data and adapting existing reporting.

• Display Alerts: have the option of storing display events in MongoDB as well as MySQL #3398

[dasgarner]

We should also have the option of creating an alert from the output of a stored command, where the alert is created based on if the command was successful, failed or always. A "never" option (default) should also be provided.

• Display Alerts: Command output #3399

[dasgarner]

Finally we should have the option of storing display events in MongoDB as well as MySQL, including migrating old data and adapting existing reporting.

This will be handled in alpha2