Computing device notification management software
Techniques disclosed herein relate to managing notifications to a user associated with a computing device. The notifications correspond to a response to an indication of an exception condition on the computing device. The response to the exception condition includes a plurality of steps, including computer-implemented steps in which data objects output a plurality of notifications for the user. These notifications are processed by a notification choreographer and used to prepare a unified status communication. The unified status communication is output to the user and depicts information corresponding to a plurality of the notifications.
1. A method comprising:
receiving, at a computer system, an indication of a trigger condition for a particular one of a plurality of internet of things (IoT) devices, the trigger condition being associated with an error detected at one or more sensors associated with mechanical and/or electrical components of the particular IoT device, wherein a response to the trigger condition includes a plurality of actions, including computer-implemented actions causing outputting of notifications for a subscriber that is associated with the particular one of the plurality of IoT devices;
controlling, responsive to receiving the indication of the trigger condition, the particular IoT device to cause the particular IoT device to shut down;
causing, by a centralized publication platform accessible by the computer system, storage of event data corresponding to the notifications for the response; and
automatically outputting, by the computer system to the subscriber, a user message combining information based on the stored event data that depicts information corresponding to the notifications.
2. The method of claim 1 , wherein controlling the particular IoT device to cause the particular IoT device to shut down comprises sending a signal to the particular IoT device, the signal causing the particular IoT device to shut down.
3. The method of claim 1 , wherein the actions specify occurrences that occur upon a rule being triggered, the actions being dynamically configurable by an authorized user associated with the computer system.
4. The method of claim 1 , wherein the actions comprise sending the event data to a database associated with the computer system.
5. The method of claim 1 , wherein the plurality of notifications for the subscriber include a first set of notifications that correspond to information to be included in the single user message and a second set of notifications that do not correspond to information to be included in the single user message.
6. The method of claim 1 ,
wherein the plurality of IoT devices communicates with the computer system over a wide area network; and
wherein the trigger condition is an indication of a malfunction in the particular IoT device and ones of the plurality of actions include steps to remedy the malfunction.
7. The method of claim 1 , wherein causing, by the centralized publication platform, storage of event data corresponding to ones of the plurality of notifications for the response includes republication of a subset of the notifications corresponding to errors associated with the particular IoT device to a dedicated topic using the centralized publication platform.
8. The method of claim 1 , further comprising:
providing access to the computer system to a plurality of entities, wherein each of the plurality of entities manages a plurality of responses to a plurality of trigger conditions for a plurality of IoT devices, the computer system being a computer system of a web services platform; and
prior to receiving the indication of the trigger condition, receiving, at the computer system, configuration information from a particular entity managing the response to the trigger condition.
9. The method of claim 1 , wherein the error comprises a temperature associated with the particular IoT device exceeding a temperature threshold.
10. The method of claim 1 , wherein the error is associated with a malfunction of the particular IoT device.
11. A non-transitory, computer-readable medium storing instructions that when executed by a computer system cause the computer system to perform operations comprising:
processing, at the computer system an indication of a trigger condition for a particular one of a plurality of internet of things (IoT) devices, the trigger condition being associated with an error detected at one or more sensors associated with mechanical and/or electrical components of the particular IoT device, wherein a response to the trigger condition includes a plurality of actions, including computer-implemented actions causing outputting of notifications for a subscriber that is associated with the particular one of the plurality of IoT devices;
controlling, responsive to receiving the indication of the trigger condition, the particular IoT device to cause the particular IoT device to shut down;
causing, by a centralized publication platform accessible by the computer system, storage of event data corresponding to the notifications for the response; and
automatically outputting, by the computer system to the subscriber, a user message combining information based on the stored event data that depicts information corresponding to the notifications.
12. The non-transitory, computer-readable medium of claim 11 , wherein controlling the particular IoT device to cause the particular IoT device to shut down comprises sending a signal to the particular IoT device, the signal causing the particular IoT device to shut down.
13. The non-transitory, computer-readable medium of claim 11 , wherein the actions specify occurrences that occur upon a rule being triggered, the actions being dynamically configurable by an authorized user associated with the computer system.
14. The non-transitory, computer-readable medium of claim 11 , wherein the actions comprise sending the event data to a database associated with the computer system.
15. The non-transitory, computer-readable medium of claim 11 , wherein the plurality of notifications for the subscriber include a first set of notifications that correspond to information to be included in the single user message and a second set of notifications that do not correspond to information to be included in the single user message.
16. A computer system comprising one or more processors, the computer system configurable to cause:
processing an indication of a trigger condition for a particular one of a plurality of internet of things (IoT) devices, the trigger condition being associated with an error detected at one or more sensors associated with mechanical and/or electrical components of the particular IoT device, wherein a response to the trigger condition includes a plurality of actions, including computer-implemented actions causing outputting of notifications for a subscriber that is associated with the particular one of the plurality of IoT devices;
controlling, responsive to receiving the indication of the trigger condition, the particular IoT device to cause the particular IoT device to shut down;
causing, by a centralized publication platform accessible by the computer system, storage of event data corresponding to the notifications for the response; and
automatically outputting, by the computer system to the subscriber, a user message combining information based on the stored event data that depicts information corresponding to the notifications.
17. The computer system of claim 16 , wherein controlling the particular IoT device to cause the particular IoT device to shut down comprises sending a signal to the particular IoT device, the signal causing the particular IoT device to shut down.
18. The computer system of claim 16 , wherein the actions specify occurrences that occur upon a rule being triggered, the actions being dynamically configurable by an authorized user associated with the computer system.
19. The computer system of claim 16 , wherein the actions comprise sending the event data to a database associated with the computer system.
20. The computer system of claim 16 , wherein the plurality of notifications for the subscriber include a first set of notifications that correspond to information to be included in the single user message and a second set of notifications that do not correspond to information to be included in the single user message.