Network management system event notification shortcut

• US 8,402,472 B2
• Filed: 09/14/2007
• Issued: 03/19/2013
• Est. Priority Date: 09/14/2007
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Appleton, Chris, Stewart, Kristian
• Primary Examiner(s): Truong, Lechi
• Application Number:
  US11/855,181
• Publication Number:
  US 20090077569A1
• Time in Patent Office: 2,013 Days
• Field of Search: 719/318
• US Class Current: 719/313
• CPC Class Codes: H04L 41/024 using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 51/226 Delivery according to priorities

Abstract

Provided is a network management system notification shortcut relating to control of an event notification shortcut in a network management system. The network management system comprising: a probe for intercepting a system event from a monitored system and creating an event item or modifying an event item associated with the system event; a collection database server for collecting a new event item or modification to an existing event item and forwarding a event notification to a second database server; a second database server for receiving the event notification, requesting the event item data or modification data and forwarding the event item to a first client; a first client for receiving the event notification and requesting the event item data or modification data; whereby the collection database server sends the event notification directly to the first client bypassing the second database server if the event satisfies a priority condition.

Claims

1. A method of managing a network comprising:

intercepting a system event from a monitored system corresponding to a stored event record;

modifying the stored event record in accordance with the system event to create a modified event record;

collecting, in a first database server the modified event record;

deleting the stored event record form the first database server such that notification corresponding to the stored event record is not transmitted to a first client;

sending an event notification from the first database server to a second database server, said event notification comprising notification of the modified event record;

sending the event notification from the second database server to the first client; and

sending the event notification from the first database server directly to the first client bypassing the second database server if the modified event record corresponds to a high priority event.

2. A method of managing a network according to claim 1 wherein if the modified event record contains a channel reference then:

identifying the channel reference in the modified event record;

identifying a client reference associated with the channel reference; and

directly notifying the referenced client of the modified event record.

3. A method of managing a network according to claim 1 wherein the collecting collects new event records and modifications to existing event records into a batch;

the notification step notifies the client of the batch of new event records and event record modifications; and

further comprising directly notifying the client of a modified event record independently of the periodic batch notification if the modified event record is a high priority system event.

4. A method according to claim 1 wherein the client comprises a gateway that receives the notifications;

pulls the modified event record from the first database server and then pushes the modified event record to a second client.

5. A method according to claim 1 wherein the collecting is performed in a collection layer by the first database server and at least one or more other collection layer database servers, each having at least one or more probes intercepting events;

the second database server client is an aggregation layer and replicates in a central location all the new event records and event modification records from the two or more collecting database servers.

6. A network management system comprising:

a processor;

a computer-readable storage medium coupled to the processor; and

computer-readable code executed on the processor, comprising;

a probe for intercepting a system event, corresponding to a stored event record, from a monitored system and creating a modified event record;

deleting the stored event record such that notification corresponding to the stored event record is not transmitted to a first client;

a collection database server for collecting the modified event record and forwarding an event notification to a second database server;

a second database server for receiving the event notification, requesting the modified event record and forwarding the received modified event record to the first client;

a first client for receiving the event notification and requesting the modified event record;

whereby the collection database server sends the event notification directly to the first client bypassing the second database server if the modified event record corresponds to a high priority system event.

7. A network management system according to claim 6, the computer-readable code further comprising:

a channel table for storing an association between a channel and a client id; and

wherein the probe associates the event item with a channel and the notifying means uses the channel table to find the client association.

8. A network management system according to claim 7 wherein the channel table further stores an association between a channel and specific fields of the new or modified event record and if the modified event record corresponds to a high priority event then further comprising directly notifying the associated client of the modified event record of the specified fields.

9. A network management system according to claim 6 wherein the collection database server collects new event records and modifications to existing event records into a batch;

the collection database server periodically notifies the second database server of the batch of new event records and event record modifications and

directly notifies the client of event record or modified event record independently of the periodic batch notification if the new or modified event record corresponds to a high priority event.

10. A network management system according to claim 6 wherein the client comprises a gateway that receives the notifications;

pulls event records from the collection database server and then pushes the event records to a second client.

11. A network management system according to claim 6, the computer-readable code further comprising a collecting layer of the collection database server and one or more other database servers, each having one or more associated probes;

the second database server is in an aggregation layer that replicates in a central location all new event records and event modification records from the two or more collecting layer database servers.

12. A computer program product comprising:

a computer-readable storage medium having computer readable code stored thereon, said computer-readable code which when loaded onto a computer system and executed performs the following;

intercepting a system event, corresponding to a stored event record, from a monitored system and creating a modified event record;

collecting, in a first database server of event records, modified event record;

deleting the stored event record form the first database server such that notification corresponding to the stored event record is not transmitted to a first client;

sending an event notification from the first database server to a second database server, said event notification comprising notification of the modified event record;

sending the event notification from the second database server to a first client; and

sending the event notification from the first database server directly to the first client bypassing the second database server if the modified event record corresponds to a high priority event.

13. A computer program product according to claim 12 wherein if the new or modified event record contains a channel reference then:

identifying the channel reference in the intercepted modified event record;

identifying a client reference associated with the channel reference; and

directly notifying the referenced client of modified event record.

14. A computer program product according to claim 12 wherein the collecting collects new event records and modifications to existing event records;

the notification notifies the client of the batch of new event records and event record modification; and

the computer-readable code further comprising directly notifying the client of a new event record or modified event record independently of the batch notification if the new or modified event record corresponds to a high priority event.

15. A computer program product according to claim 12 wherein the client comprises a gateway that receives the notifications;

pulls an event record from the first database server and then pushes the event record to a second client.

16. A computer program product according to claim 12 wherein the collecting is performed in a collection layer by the first database server and at least one or more other collection layer database servers, each having at least one or more probes intercepting events;

the second database server client is an aggregation layer and replicates in a central location all new event records and/or event modification records from the two or more collecting database servers.