Event monitoring system and method

• US 20040117802A1
• Filed: 12/13/2002
• Published: 06/17/2004
• Est. Priority Date: 12/13/2002
• Status: Active Grant

• Current Assignee: Colorado WSC, LLC
• Original Assignee: Wells Fargo Foothill, LLC (Wells Fargo & Company)
• Inventors: Green, James D.
• Granted Patent: US 7,552,445 B2
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G05B 2219/32034 Electronic market, network broker
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/302 where the computing system component is a software system
• CPC Class Codes: G06F 11/3072 where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
• CPC Class Codes: G06Q 10/06311 Scheduling, planning or task assignment for a person or group
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]

Abstract

An event monitoring system and method that monitors and reports the data events occurring throughout an enterprise using an event monitor. The event monitor receives data event information from one or more brokers, captures data event information, and outputs the data event information to a user.

Claims

1. An event monitor comprising:

a computing system including a processor, the processor being configured to receive data event information, wherein

the computing system is coupled to one or more enterprise brokers using a network, the processor is configured to generate an incoming events list including the data event information received from each of the enterprise brokers, and the computing system includes a user interface configured to output the incoming events list to a user.

2. The event monitor of claim 1, wherein the processor is further configured to maintain connections to the one or more enterprise brokers.

3. The event monitor of claim 2, further comprising a listener associated with each of the connections, the listener being configured to detect a desired set of data events.

4. The event monitor of claim 1, further comprising an event database operably coupled to the computing system, and wherein the processor is further configured to store data events using the event database.

5. The event monitor of claim 1, in which the processor is further configured to simulate the flow of data events throughout an enterprise.

6. An event monitor comprising:

a computer system including a processor, the computer system being connected to one or more enterprise brokers using a network, the computer system further including a server listener module and a corresponding client listener module for each broker connection, wherein the client listener module is configured to detect data events flowing through the broker, the computer system further including an event tracking module to configure the processor to receive data event information from the enterprise brokers via the network and to generate an incoming events list including the data event information received from the enterprise brokers, the computer system further including a simulation module to configure the processor to determine propagation times for simulated events flowing though at least one broker and at least one broker client or application according to at least one communication topology, the event tracking module further configured to cause the processor to generate a historical events list based on user input data event parameters in response to a user selection, the computer system further including a user interface module to configure the processor to output the incoming events list, simulation results, and historical events list to a user.

7. The event monitor of claim 6, further comprising an event database including a broker connections property file containing broker connection information, and wherein the processor is further configured to store data events using the event database.

8. The event monitor of claim 6, wherein the user interface module further includes a graphical user interface, the graphical user interface being configured to output a monitor page containing an incoming events list to a user.

9. The event monitor of claim 6, wherein the simulation module is further configured to compare publication times and includes a simulation report generator.

10. The event monitor of claim 6, wherein the event tracking module data event parameters further include a work order number.

11. An event monitoring method comprising:

configuring a listener to detect the occurrence of data events at an enterprise broker;

establishing a connection to one or more enterprise brokers;

detecting the occurrence of one of a particular set of data events at an enterprise broker; and

outputting data event information associated with the detected data event to an event monitor.

12. The method of claim 11, further comprising:

maintaining a persistent copy of the data event information at the event monitor;

storing the data event information using a database;

updating an incoming events list in response to receiving the detected data event; and

outputting the incoming events list to a user.

13. The method of claim 12, wherein the updating an incoming events list is performed in response to receiving new data event information.

14. The method of claim 12, wherein the updating an incoming events list is performed periodically.

15. The method of claim 12, wherein the outputting the incoming events list to the user is accomplished using a graphical user interface.

16. The method of claim 11, further comprising:

simulating the flow of simulated data events throughout an enterprise according to at least one communication topology;

determining the propagation times of simulated data events; and

comparing the publication times of simulated data events.

17. The method of claim 11, further comprising generating a historical events list based on user input data event parameters in response to a user selection.

18. The method of claim 11, wherein the detecting is accomplished using a listener module.

19. The method of claim 11, wherein the establishing a connection includes reading a broker connections property file containing broker connection information.

20. An event monitoring system comprising:

an event monitor including a computer system; and

one or more enterprise brokers coupled to the event monitor using a network, each of the enterprise brokers including a client listener module configured to detect the occurrence of data events at the broker, each enterprise broker coupled to at least one broker client or application using a network, wherein the event monitor is configured to receive data event information from each broker via the listener module and to generate an incoming events list including the data event information received from each of the enterprise brokers.

21. The event monitoring system of claim 20, further comprising an event database operably coupled to the event monitor, and wherein the event monitor is further configured to store data events using the event database.

22. The event monitoring system of claim 20, in which the event monitor is further configured to simulate the flow of data events throughout an enterprise.

23. The event monitoring system of claim 20, in which the event monitor is further configured to generate a historical events list based on user input data event parameters in response to a user selection.

24. An event monitor comprising:

data event monitoring means coupled to one or more enterprise brokers using a network and configured to receive data event information from the brokers and to generate an incoming events list including the received data event information, each of the enterprise brokers further including listening means for detecting the occurrence of a data event at the broker;

an event database operably coupled to the data event monitoring means for storing data event information; and

a user interface configured to output the incoming events list to a user.

25. The event monitor of claim 24, further comprising simulation means for simulating the flow of data events throughout an enterprise.

26. The event monitor of claim 24, in which the data event monitoring means is further configured to generate a historical events list based on user input data event parameters in response to a user selection.

27. A computer-readable medium upon which is embodied a set of programmable instructions that when executed cause a processor to:

establish a connection to one or more enterprise brokers;

detect the occurrence of one of a particular set of data events at an enterprise broker;

output data event information associated with the detected data event to an event monitor;

maintain a persistent copy of the data event information at the event monitor;

store the data event information using a database;

update an incoming events list in response to receiving the detected data event; and

output the incoming events list to a user.

28. The computer-readable medium of claim 27, further configured to cause a processor to update the incoming events list in response to receiving new data event information.

29. The computer-readable medium of claim 27, further configured to cause a processor to update the incoming events list periodically.

30. The computer-readable medium of claim 27, further configured to cause a processor to:

simulate the flow of simulated data events throughout an enterprise according to at least one communication topology;

determine the propagation times of simulated data events; and

compare the publication times of simulated data events.

31. The computer-readable medium of claim 27, further configured to cause a processor to generate a historical events list based on user input data event parameters in response to a user selection.

32. The computer-readable medium of claim 27, further configured to cause a processor to establish a connection includes to one or more enterprise brokers by reading a broker connections property file containing broker connection information.