Event processing systems and methods

Patent metadata

Field	Value
Publication number	US-12517772-B2
Application number	US-202217854937-A
Country	US
Kind code	B2
Filing date	Jun 30, 2022
Priority date	Jun 30, 2022
Publication date	Jan 6, 2026
Grant date	Jan 6, 2026

Abstract

Systems and methods for processing event records are disclosed. The method includes receiving, at a server node, an event record. The event record includes an event type identifier. The method further includes selecting a message queue from a plurality of message queues for the event record based at least on the event type identifier of the event record, and communicating the event record to the selected message queue. A worker node associated with the selected message queue retrieves the event records, processes it and communicates the processed event record to a downstream service for consumption.

First claim

What is claimed is:

1 . A computer-implemented method comprising:
receiving, at a server node, an event record, the event record generated in response to a user interaction with a client application operating on a client device; assigning, by the server node, a priority level to the event record based on a type of interaction with the client application causing the event record; selecting a message queue from a plurality of message queues for the event record based at least on the priority level, each message queue having a respective priority level for processing event records, wherein the system is configured to process a higher priority level event record before a lower priority level event record; communicating the event record to the selected message queue; and causing processing, by a worker node associated with the selected message queue, the event record and communicating to a downstream service for consumption, wherein a worker node processing event records in a high priority queue is different than a worker node processing event records in a low priority queue.

2 . The computer-implemented method of claim 1 , wherein the type of interaction causing the event record indicates whether the event record is for a trait event, a behavior event, or an operational event.

3 . The computer-implemented method of claim 2 , wherein:
the plurality of messages queues include a priority queue and a standard queue; the server node selects the priority queue upon determining that the type of interaction causing the event record indicates that the event record is for the trait event; and the server node selects the standard queue upon determining that the type of interaction causing the event record indicates that the event record is for the behavior event or the operational event.

4 . The computer-implemented method of claim 1 , further comprising:
retrieving the priority of the event record from an event database; and adding the retrieved priority to the event record.

5 . The computer-implemented method of claim 1 , wherein the selecting the message queue for the event record includes selecting the message queue based on one or more external factors.

6 . The computer-implemented method of claim 5 , wherein the one or more external factors include time of day or number of event records present in the plurality of message queues.

7 . The computer-implemented method of claim 1 , further comprising:
determining whether the event record is valid; and discarding the event record upon determining that the event record is invalid.

8 . The computer-implemented method of claim 1 , further comprising enriching the event record, wherein enriching the event record includes at least one of:
adding a priority field to the event record that indicates the priority of the event record; adding information about an operating system of a client device on which the event record was generated; or adding location information of the client device on which the event record was generated.

9 . An event processing system, comprising:
a server node; a plurality of message queues; and a worker node associated with each of the plurality of message queues; wherein:
the server node comprises a first processing unit and a first non-transitory computer readable medium comprising instructions which when executed by the first processing unit cause the server node to:
receive an event record, the event record generated in response to a user interaction with a client application operating on a client device;
assign, by the server node, a priority level to the event record based on a type of interaction with the client application causing the event record;
select a message queue from the plurality of message queues for the event record based at least on the priority level, each message queue having a respective priority level for processing event records, wherein the system is configured to process a higher priority level event record before a lower priority level record; and
communicate the event record to the selected message queue; and

the worker node associated with the selected message queue comprises a second processing unit and a second non-transitory computer readable medium comprising instructions which when executed by the second processing unit cause the worker node to:
process the event record, wherein a worker node processing event records in a high priority queue is different than a worker node processing event records in a low priority queue; and
communicate the processed event record to a downstream service for consumption.

10 . The event processing system of claim 9 , wherein the type of interaction causing the event record indicates whether the event record is for a trait event, a behavior event, or an operational event.

11 . The event processing system of claim 10 , wherein:
the plurality of messages queues include a priority queue and a standard queue; the server node selects the priority queue upon determining that the type of interaction causing of the event record indicates that the event record is for the trait event; and the server node selects the standard queue upon determining that the type of interaction causing the event record indicates that the event record is for the behavior event or the operational event.

12 . The event processing system of claim 9 , wherein the first non-transitory computer readable medium further comprising instructions which when executed by the first processing unit cause the server node to:
retrieve the priority of the event record from an event database; and add the retrieved priority to the event record.

13 . The event processing system of claim 9 , wherein the selecting the message queue for the event record includes selecting the message queue based on one or more external factors.

14 . The event processing system of claim 13 , wherein the one or more external factors include time of day or number of event records present in the plurality of message queues.

15 . The event processing system of claim 9 , wherein the first non-transitory computer readable medium further comprising instructions which when executed
by the first processing unit cause the server node to:
determine whether the event record is valid; and
discard the event record upon determining that the event record is invalid.

16 . The event processing system of claim 9 , wherein the first non-transitory computer readable medium further comprising instructions which when executed by the first processing unit cause the server node to enrich the event record, wherein enriching the event record includes at least one of:
adding a priority field to the event record that indicates the priority of the event record; adding information about an operating system of a client device on which the event record was generated; or adding location information of the client device on which the event record was generated.

Assignees

• Atlassian Pty Ltd
• Atlassian Inc
• Atlassian Us Inc

Inventors

• Rahman Saidur
• Zhang Xinyang

Classifications

• G06F9/546 Primary

  Message passing systems or structures, e.g. queues · CPC title

• G06F9/542 Primary

  Event management; Broadcasting; Multicasting; Notifications · CPC title