Method and system for intelligent global event notification and control within a distributed computing environment

• US 6,829,639 B1
• Filed: 11/15/1999
• Issued: 12/07/2004
• Est. Priority Date: 11/15/1999
• Status: Expired due to Term

• Current Assignee: F Poszat Hu LLC (Intellectual Ventures LLC)
• Original Assignee: Netvision Limited (Cellcom Israel Limited)
• Inventors: Cave, Warren D., Lawson, Todd C., Fisher, Kamika Layne
• Primary Examiner(s): Harvey, Jack
• Assistant Examiner(s): Nguyen, Hai V.
• Application Number:
  US09/440,620
• Time in Patent Office: 1,849 Days
• Field of Search: 709/201, 709/202, 709/203, 709/204, 709/223, 709/224, 709/227, 707/10, 714/25, 714/37, 714/48, 714/51, 714/57
• US Class Current: 709/224
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 43/028 by filtering
• CPC Class Codes: H04L 43/045 for graphical visualisation of monitoring data
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A distributed computer environment (DCE) is disclosed that provides event globalizing of at least one event at one server in the DCE to other servers within said DCE as well as maintains a record of specific event activity over the DCE. The maintenance of the records is performed by storing a global event file comprising a list of events and a corresponding list of servers in order to identify which of the servers should receive which events, storing a local event registry comprising a list of events and a corresponding list of local event consumers in order to identify which of the local event consumers should receive which events, identifying specific events within the list of events to be monitored for a specific purpose, monitoring said specific events as they occur over the DCE, notifying a specific local event consumer of the occurrence of the specific events, and recording a log of event activity involving only the specific events.

Claims

1. In a distributed computer environment (DCE) that provides event globalizing of at least one event at one server in said DCE to other servers within said DCE, a method of maintaining a record of specific event activity over said DCE comprising:

storing a global event repository comprising a list of events and a corresponding list of servers in order to identify which of said servers should receive which events;

storing a local event registry comprising a list of events and a corresponding list of event consumers in order to identify which of said event consumers should receive which events;

defining specific types of events within the list of events that are to be monitored for a specific purpose;

providing settings of the defined specific events in a plurality of registration lists;

monitoring said specific events passed from one controller to another controller of said DCE;

automatically determining if said passed specific events conform with any of the settings of the defined specific events;

notifying a specific event consumer of the occurrence of said specific events that meet a criteria of said specific purpose;

using said specific event consumer to automatically report the occurrence of said specific events that meet a criteria of said specific purpose by using one of a plurality of filters that are independently defined in accordance with pre-established criteria, wherein the filter used is associated with said specific event consumer to determine which final event consumer is to receive said report and in which of a plurality of available formats said report is provided; and

recording a log of event activity involving only said specific events.

2. A method of observing events as recited in claim 1 further comprising the step of storing filtering criteria that is used to filter specific events that occur so that only notification of events meeting the stored filtering criteria is sent.

3. A method of observing events as recited in claim 2 wherein said stored filtering criteria specifies at least one event consumer and the filtering criteria associated with the at least one event consumer.

4. A method of observing events as recited in claim 1 wherein said global event registry is accessible to a plurality of servers so that each of said plurality of servers can access the list of events and the corresponding list of servers stored in said global event registry.

5. A method of observing events as recited in claim 1 wherein said global event registry is distributed across a plurality of servers and wherein said plurality of servers can access said global event registry to retrieve desired information therefrom.

6. A method of observing events as recited in claim 1 further comprising the step of registering for an event by placing an entry into at least one of said global event registry or said local event registry, said entry comprising a server and a corresponding event if said entry is placed in said global event registry and said entry comprising a event consumer and a corresponding event if said entry is placed in said local event registry.

7. A method of observing events as recited in claim 1 further comprising the step of creating a new event type by placing an entry into at least one of said global event registry or said local event registry, said entry comprising a server and a corresponding new event type if said entry is placed in said global event registry and said entry comprising a event consumer and a corresponding new event type if said entry is placed in said local event registry.

8. A method of observing events as recited in claim 1 wherein the notifying step further comprises notifying a system administrator of the specific event.

9. A method of observing events as recited in claim 1 wherein the recording step comprises recording information regarding the specific events.

10. A method of observing events as recited in claim 9 wherein the recorded information is selected from the list comprising:

time of occurrence, event source type, setting name, event name, class name, perpetrator, originating server, attribute name, attribute value.

11. In a distributed computer environment (DCE) that provides event globalizing of at least one event at one server in said DCE to other servers within said DCE, a method of maintaining a record of specific event activity over said DCE comprising:

storing a global event repository comprising a list of events and a corresponding list of servers in order to identify which of said servers should receive which events;

storing a local event registry comprising a list of events and a corresponding list of event consumers in order to identify which of said event consumers should receive which events;

defining specific types of events within the list of events that are to be automatically monitored for a specific purpose;

providing settings of the defined specific events in a plurality of registration lists;

monitoring said specific events passed from one controller to another controller of said DCE;

automatically determining if said passed specific events conform with any of the settings of the defined specific events;

automatically updating the local event registry based upon authorized changes to a given event or event consumer;

notifying a specific event consumer of the occurrence of said specific events that meet a criteria of said specific purpose;

using said specific event consumer to automatically report the occurrence of said specific events that meet a criteria of said specific purpose by using one of a plurality of filters that are independently defined in accordance with pre-established criteria, wherein the filter used is associated with said specific event consumer to determine which final event consumer is to receive said report and in which of a plurality of available formats said report is provided, wherein said plurality of available formats include a text file, a database and an email; and

recording a log of event activity involving only said specific events.

12. A method of observing events as recited in claim 11 further comprising the step of storing filtering criteria that is used to filter specific events that occur so that only notification of events meeting the stored filtering criteria is sent.

13. A method of observing events as recited in claim 12 wherein said stored filtering criteria specifics at least one event consumer and the filtering criteria associated with the at least one event consumer.

14. A method of observing events as recited in claim 11 wherein said global event registry is accessible to a plurality of servers so that each of said plurality of servers can access the list of events and the corresponding list of servers stored in said global event registry.

15. A method of observing events as recited in claim 11 wherein said global event registry is distributed across a plurality of servers and wherein said plurality of servers can access said global event registry to retrieve desired information therefrom.

16. A method of observing events as recited in claim 11 wherein said notifying step further comprises evaluating a set of rules to determine the specific event consumer to notify.

17. A method of observing events as recited in claim 11 wherein said notifying step further comprises filtering said specific event to match said specific event to an appropriate event consumer.

18. A method of observing events as recited in claim 11 wherein the notifying step further comprises notifying a system administrator of the specific event.

19. A method of observing events as recited in claim 11 wherein the recording step comprises recording information regarding the specific events.

20. A method of observing events as recited in claim 19 wherein the recorded information is selected from the list comprising:

time of occurrence, event source type, setting name, event name, class name, perpetrator, originating server, attribute name, attribute value.

21. In a distributed computer environment (DCE) that provides event globalizing of at least one event at one server in said DCE to other servers within said DCE, a method of maintaining a record of specific event activity over said DCE comprising:

storing a global event repository comprising a list of events and a corresponding list of servers in order to identify which of said servers should receive which events;

storing a local event registry comprising a list of events and a corresponding list of event consumers in order to identify which of said event consumers should receive which events;

identifying specific types of events within the list of events that are to be monitored for a specific purpose;

providing settings of the identified specific events in a plurality of registration lists;

monitoring said specific events passed from one controller to another controller of said DCE;

automatically determining if said passed specific events conform with any of the settings of the identified specific events;

automatically updating the local event registry based upon authorized changes to a given event or event consumer;

notifying a specific event consumer of the occurrence of said specific events that meet a criteria of said specific purpose;

using said specific event consumer to automatically report the occurrence of said specific events that meet a criteria of said specific purpose by using one of a plurality of filters that are independently defined in accordance with pre-established criteria, wherein the filter used is associated with said specific event consumer to determine which final event consumer is to receive said report and in which of a plurality of available formats said report is provided;

revoking a specific event that is not authorized; and

recording a log of event activity involving only said specific events.

22. A method of observing events as recited in claim 21 further comprising the step of storing filtering criteria that is used to filter specific events that occur so that only notification of events meeting the stored filtering criteria is sent.

23. A method of observing events as recited in claim 22 wherein said stored filtering criteria specifies at least one event consumer and the filtering criteria associated with the at least one event consumer.

24. A method of observing events as recited in claim 21 wherein said global event registry is accessible to a plurality of servers so that each of said plurality of servers can access the list of events and the corresponding list of servers stored in said global event registry.

25. A method of observing events as recited in claim 21 wherein said global event registry is distributed across a plurality of servers and wherein said plurality of servers can access said global event registry to retrieve desired information therefrom.

26. A method of observing events as recited in claim 21 wherein said notifying step further comprises evaluating a set of rules to determine the specific event consumer to notify and which specific events are unauthorized.

27. A method of observing events as recited in claim 21 wherein said notifying step further comprises filtering said specific event to match said specific event to an appropriate event consumer.

28. A method of observing events as recited in claim 21 wherein the notifying step further comprises notifying a system administrator of the unauthorized specific event.

29. A method of observing events as recited in claim 21 wherein the recording step comprises recording information regarding the specific events.

30. A method of observing events as recited in claim 29 wherein the recorded information is selected from the list comprising:

time of occurrence, event source type, setting name, event name, class name, perpetrator, originating server, attribute name, attribute value.

31. A distributed computer environment (DCE) system comprising:

a system directory;

a least one server, coupled to the system directory;

at least one global event services controller, coupled to the system directory, to globalize at least one event at said at least one server to other servers within said DCE, wherein a local event registry is stored maintained by the at least one global event services controller, the local event registry comprising a list of events and a corresponding list of servers in order to identify which of said servers should receive which events and a list of events and a corresponding list of event consumers that identify which of said event consumers should receive which local events;

a data alert controller, coupled to said at least one global event services controller, to monitor specific events passed from the global event services controller to the data alert controller of the DCE, to notify a specific event consumer of the occurrence of the specific events, and to record a log of event activity involving only said specific events, wherein said specific events meet a criteria of a specific purpose; and

at least one of a plurality of filters that are independently defined in accordance with pre-established criteria wherein the filter is communicatively coupled to said data alert controller to determine which final event consumer is to receive a report of said specific events and in which of a plurality of available formats said report is provided.

32. The DCE system as recited in claim 31 further comprising at least one filter, associated with each specific event consumer and coupled to the data alert controller, to filter specific events using defined filtering criteria so that only notification of events meeting the stored filtering criteria is sent.

33. The DCE system as recited in claim 32 wherein said stored filtering criteria specifies at least one event consumer and the filtering criteria associated with the at least one event consumer.

34. The DCE system as recited in claim 31 wherein said global event registry is accessible to a plurality of servers so that each of said plurality of servers can access the list of events and the corresponding list of servers stored in said global event registry.

35. The DCE system as recited in claim 31 wherein said global event registry is distributed across a plurality of servers and wherein said plurality of servers can access said global event registry to retrieve desired information therefrom.

36. The DCE system as recited in claim 31 further comprising a rules controller, coupled to the data alert controller to evaluate a set of rules to determine the specific event consumer to notify and which specific events are unauthorized.

37. The DCE system as recited in claim 31 further comprising a registration filter, coupled to the data alert controller, to filter said specific event to match said specific event to an appropriate event consumer.

38. The DCE system of claim 31 wherein the data alert controller also notifies a system administrator of the unauthorized specific event.

39. The DCE system of claim 31 wherein the log record comprises information regarding the specific events.

40. The DCE system as recited in claim 39 wherein the information is selected from the list comprising:

time of occurrence, event source type, setting name, event name, class name, perpetrator, originating server, attribute name, attribute value.

41. The DCE system as recited in claim 31 wherein the global event services controller updates the local event registry based upon authorized changes to a given event or event consumer.

42. The DCE system as recited in claim 31 wherein the data event controller revokes a specific event that is not authorized.

43. The DCE system as recited in claim 36 wherein each event consumer utilizes the set of rules to determine what action to take.