Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

The AMQP service allows the recipient to track the continuity of the relation. By means of messages of the "event_keep_alive" type, it is possible to react quickly to any problems with data transmission. Event_keep_alive messages are sent to ensure connectivity of a feed. This information should also be used by a receiver of the feed to monitor the feed status.

Every 30 seconds you should receive at least 1 message from each live event. The AMQP service will be sending messages for a particular event at the earliest, 30 minutes before the event start time (when the scout will change the relation status from “Not started” to “30 min left”) up until the end of the event when the scout confirms the result.

Message example:

Structure - event_keep_alive
{
  "id": -1,
  "uuid": null,
  "type": "event_keep_alive",
  "source": 1148,
  "ut": 1611574713,
  "data": {
    "event_keep_alive": {
      "event_id": 3755129,
      "clock_time": 482,
      "clock_status": "running"
    }
  }
}

Message structure details:

.message
idInteger value = -1
uuidUniversally unique identifier
type

event_keep_alive

sourceInternal attribute
utInformation about the date and time of when the message was created. Format UNIX_TIMESTAMP
..data
...event_keep_alive
event_idinteger value, Identifier of the event.
clock_time

Period time, counted from 0 for each game period. Possible values:

  • integer
  • Null, Null is sent in the sports that don't require clock.
clock_status

Possible values:

  • "stopped"
  • "running"
  • Null, Null is sent in the sports that don't require clock.




  • No labels