Edge alert coordinator for mobile devices

1. A system, comprising:

at least one computing device; and

program instructions stored in at least one memory of the at least one computing device, wherein the instructions, when executed by at least one processor, cause the at least one computing device to at least:

receive, by an edge device, from a device connected to a network through the edge device, an identifier of a previous edge device through which the device previously connected;

store, by the edge device, a pending status in association with the device, wherein the pending status causes the edge device to queue device data received from the device until inherited device alert data is received from the previous edge device;

monitor, by the edge device, the device data received from the device, wherein the edge device queues the device data based at least in part on the pending status;

transmit, by the edge device, at least one join message that indicates the device has connected to the network, and comprises a device identifier of the device;

receive, by the edge device, the inherited device alert data inherited from the previous edge device, wherein the inherited device alert data comprises an alert-prerequisite device state monitored by the previous edge device based on an alert definition that specifies a plurality of alert-prerequisite device states; and

trigger an alert corresponding to the alert definition based on the plurality of alert-prerequisite device states, the plurality of alert-prerequisite device states comprising: the alert-prerequisite device state monitored by the previous edge device, and the device data monitored by the edge device.

2. The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:

transmit, by the edge device to the previous edge device, the at least one join message exclusively to the previous edge device identified by the device.

3. The system of claim 1 , wherein the previous edge device deletes the alert definition and the alert-prerequisite device state based at least in part on receiving the at least one join message from the edge device.

4. The system of claim 3 , wherein the edge device is unable to directly communicate with the previous edge device and the at least one join message is relayed through a back-end evaluation service.

5. The system of claim 3 , wherein the inherited device alert data is received from a back-end evaluation service.

6. The system of claim 1 , wherein the inherited device alert data comprises: at least one alert definition for the device, and inherited alert state data for the device.

7. The system of claim 1 , wherein the at least one join message comprises an identifier of the edge device.

8. A method, comprising:

receiving, by an edge device from, a device connected to a network through the edge device, an identifier of a previous edge device through which the device previously connected;

storing, by the edge device, a pending status in association with the device, wherein the pending status causes the edge device to queue device data received from the device until inherited device alert data is received from the previous edge device;

monitoring, by the edge device, the device data received directly from the device, wherein the edge device queues the device data based at least in part on the pending status;

transmitting, by the edge device, at least one join message that indicates the device has connected to the network, and comprises a device identifier of the device;

receiving, by the edge device, the inherited device alert data inherited from the previous edge device, wherein the inherited device alert data comprises an alert-prerequisite device state monitored by the previous edge device based on an alert definition that specifies a plurality of alert-prerequisite device states; and

triggering an alert corresponding to the alert definition based on the plurality of alert-prerequisite device states, the plurality of alert-prerequisite device states comprising: the alert-prerequisite device state monitored by the previous edge device, and the device data monitored by the edge device.

9. The method of claim 8 , further comprising:

transmitting, by the edge device to the previous edge device, the at least one join message exclusively to the previous edge device identified by the device.

10. The method of claim 8 , wherein the previous edge device deletes the alert definition and the alert-prerequisite device state based at least in part on receiving the at least one join message from the edge device.

11. The method of claim 10 , wherein the edge device is unable to directly communicate with the previous edge device and the at least one join message is relayed through a back-end evaluation service.

12. The method of claim 10 , wherein the inherited device alert data is received from a back-end evaluation service.

13. The method of claim 8 , wherein the inherited device alert data comprises: at least one alert definition for the device, and inherited alert state data for the device.

14. The method of claim 8 , wherein the at least one join message comprises an identifier of the edge device.

15. A non-transitory computer-readable medium comprising program instructions that when executed by at least one processor, cause at least one computing device to at least:

receive, by an edge device from, a device connected to a network through the edge device, an identifier of a previous edge device through which the device previously connected;

store, by the edge device, a pending status in association with the device, wherein the pending status causes the edge device to queue device data received from the device until inherited device alert data is received from the previous edge device;

monitor, by the edge device, the device data received from the device, wherein the edge device queues the device data based at least in part on the pending status;

transmit, by the edge device, at least one join message that indicates the device has connected to the network, and comprises a device identifier of the device;

receive, by the edge device, the inherited device alert data inherited from the previous edge device, wherein the inherited device alert data comprises an alert-prerequisite device state monitored by the previous edge device based on an alert definition that specifies a plurality of alert-prerequisite device states; and

trigger an alert corresponding to the alert definition based on the plurality of alert-prerequisite device states, the plurality of alert-prerequisite device states comprising: the alert-prerequisite device state monitored by the previous edge device, and the device data monitored by the edge device.

16. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:

transmit, by the edge device to the previous edge device, the at least one join message exclusively to the previous edge device identified by the device.

17. The non-transitory computer-readable medium of claim 15 , wherein the previous edge device deletes the alert definition and the alert-prerequisite device state based at least in part on receiving the at least one join message from the edge device.

18. The non-transitory computer-readable medium of claim 17 , wherein the edge device is unable to directly communicate with the previous edge device and the at least one join message is relayed through a back-end evaluation service.

19. The non-transitory computer-readable medium of claim 17 , wherein the inherited device alert data is received from a back-end evaluation service.

20. The non-transitory computer-readable medium of claim 15 , wherein the inherited device alert data comprises: at least one alert definition for the device, and inherited alert state data for the device.