Systems and methods for real-time processing and transmitting of high-priority notifications
Systems and methods are disclosed for secure transmission of high-priority computer server event notifications. One method comprises obtaining a new computer server event to report; generating a first notification message pertaining to the computer server event; generating a second notification message pertaining to the computer server event and to the delivery of the first notification message; storing the first notification message; storing the second notification message; and transmitting the first notification message to a partner over a computer network.
1. A method for secure transmission of high-priority computer server event notifications, the method comprising:
receiving server event information from a notification source;
performing a create event operation based on the server event information;
generating i) a high-priority notification message based on one or more data components collected via the create event operation and ii) a delayed delivery message;
transmitting the high-priority notification message to a first queue client;
transmitting the delayed delivery message to a second queue client;
transmitting the high-priority notification message in the first queue client to a partner system via a security protocol, the security protocol being one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS);
determining whether an acknowledgment message is received from the partner system;
denoting the high-priority notification message as sent based on determining that the acknowledgement is received from the partner system; and
removing the delayed delivery message from the second queue client based on determining that the acknowledgement is received from the partner system.
2. The method of claim 1 , wherein the one or more data components collected via the create event operation comprise one or more of: a notification identifier (ID), a notification type, and notification details.
3. The method of claim 1 , wherein the delayed delivery message indicates a notification error.
4. The method of claim 1 , wherein the high-priority notification message comprises one or more of: an event type, case information, control information, device information, contact information, transaction information, or a variable list.
5. The method of claim 4 , wherein the high-priority notification message further comprises information on whether there has been opt-out of reporting to a downstream system.
6. The method of claim 1 , wherein the acknowledgement is received concurrently with a status update.
7. The method of claim 6 , wherein the status update includes a case update.
8. The method of claim 6 , further comprising:
determining whether the status update regarding the server event is received from the partner system;
in lieu of removing the delayed delivery message from the second queue client, de-queuing the delayed delivery message based on determining that the update is not received from the partner system; and
transmitting the delayed delivery message to a downstream system.
9. The method of claim 1 , further comprising, based on the acknowledgement not being received:
in lieu of removing the delayed delivery message from the second queue client, de-queuing the delayed delivery message based on a predetermined time threshold; and
transmitting the delayed delivery message to a downstream system.
10. The method of claim 9 , wherein the delayed delivery message is transmitted to the downstream system based on a service level agreement.
11. A system for secure transmission of high-priority computer server event notifications, the system comprising:
one or more processors; and
one or more computer readable media comprising instructions which, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
receiving server event information from a notification source;
performing a create event operation based on the server event information;
generating i) a high-priority notification message based on one or more data components collected via the create event operation and ii) a delayed delivery message;
transmitting the high-priority notification message to a first queue client;
transmitting the delayed delivery message to a second queue client;
transmitting the high-priority notification message in the first queue client to a partner system via a security protocol, the security protocol being one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS);
determining whether an acknowledgment message is received from the partner system;
denoting the high-priority notification message as sent based on determining that the acknowledgement is received from the partner system; and
removing the delayed delivery message from the second queue client based on determining that the acknowledgement is received from the partner system.
12. The system of claim 11 , wherein the one or more data components collected via the create event operation comprise one or more of: a notification identifier (ID), a notification type, and notification details.
13. The system of claim 11 , wherein the delayed delivery message indicates a notification error.
14. The system of claim 11 , wherein the high-priority notification message comprises one or more of: an event type, case information, control information, device information, contact information, transaction information, or a variable list.
15. The system of claim 14 , wherein the high-priority notification message further comprises information on whether there has been opt-out of reporting to a downstream system.
16. The system of claim 11 , wherein the acknowledgement is received concurrently with a status update.
17. The system of claim 16 , wherein the status update includes a case update.
18. The system of claim 16 , the operations further comprising:
determining whether the status update regarding the server event is received from the partner system;
in lieu of removing the delayed delivery message from the second queue client, de-queuing the delayed delivery message based on determining that the update is not received from the partner system; and
transmitting the delayed delivery message to a downstream system.
19. The system of claim 16 , further comprising, based on the acknowledgement not being received:
in lieu of removing the delayed delivery message from the second queue client, de-queuing the delayed delivery message based on a predetermined time threshold; and
transmitting the delayed delivery message to a downstream system.
20. One or more non-transitory computer readable media comprising instructions which, when executed by one or more processors, cause the one or more processors to perform operations for secure transmission of high-priority computer server event notifications, the operations comprising:
receiving server event information from a notification source;
performing a create event operation based on the server event information;
generating i) a high-priority notification message based on one or more data components collected via the create event operation and ii) a delayed delivery message;
transmitting the high-priority notification message to a first queue client;
transmitting the delayed delivery message to a second queue client;
transmitting the high-priority notification message in the first queue client to a partner system via a security protocol, the security protocol being one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS);
determining whether an acknowledgment message is received from the partner system;
denoting the high-priority notification message as sent based on determining that the acknowledgement is received from the partner system; and
removing the delayed delivery message from the second queue client based on determining that the acknowledgement is received from the partner system.