...
...
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:
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"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 | |
|---|---|
| id | Integer value = -1 |
| uuid | Universally unique identifier |
| type | event_keep_alive |
| source | Internal attribute |
| ut | Information about the date and time of when the message was created. Format UNIX_TIMESTAMP |
| ..data | |
| ...event_keep_alive | |
| event_id | integer value, Identifier of the event. |
| clock_time | Period time, counted from 0 for each game period. Possible values:
|
| clock_status | Possible values:
|
...