Network management event storage and manipulation using relational database technology in a data warehouse

• US 6,138,121 A
• Filed: 05/29/1998
• Issued: 10/24/2000
• Est. Priority Date: 05/29/1998
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Costa, Brian, Das, Chris P., Kepner, William C.
• Primary Examiner(s): Breene, John
• Assistant Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US09/087,203
• Time in Patent Office: 879 Days
• Field of Search: 707/104, 707/100, 707/10, 707/500, 707/513, 709/201
• US Class Current: 1/1
• 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/0677 Localisation of faults
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A data schema and method for storing network management system event data to allow efficient retrieval of information and aggregation for use in tracking system trends and generating useful reports is presented. The invention provides a standardized system event format that is generically available to the user through standard interfaces, along with a method for populating it. The data is easily accessible via standard interfaces to statistical process control, trend tracking, and report generating applications, which present information of interest relating to the events in a useful manner to thereby increase its value.

Claims

1. A method for storing network management system events, each of said events comprising one of a plurality of different event types, comprising:

receiving a network management system event, said network management system event comprising a plurality of event fields;

extracting at least a first set of said plurality of event fields from said network management system event;

storing said first set of said event fields in a report-ready table in a relational database, said report-ready table capable of storing multiple events and used by a report generator to generate a report, and said first set of said event fields comprising each of said plurality of event fields that are essential for generation of said report.

2. A method in accordance with claim 1, comprising:

extracting a second set of said plurality of event fields from said network management system event; and

storing said second set of said event fields in a detail table, said second set of said event fields comprising at least one of said plurality of event fields that are common to all of said event types.

3. A method in accordance with claim 2, comprising:

extracting a third set of said plurality of event fields from said network management system event;

storing a third set of said event fields in a variable binding table, said third set of said event fields comprising at least one of said plurality of event fields that are not common to all of said event types; and

wherein said detail table comprises a link to said variable binding table.

4. A method in accordance with claim 3, wherein:

said second set of said plurality of event fields and said third set of said plurality of event fields together comprise all of said plurality of event fields.

5. A method in accordance with claim 1, comprising:

receiving a report query from said report generator; and

sending said first set of said said plurality of event fields to said report generator.

6. A method in accordance with claim 2, comprising:

receiving a detail query from a process; and

returning said second set of said plurality of event fields from said detail table to said process.

7. A method in accordance with claim 3, comprising:

receiving a full detail query from a process, said full detail query requiring all available information about said event; and

returning said second set of said plurality of event fields from said detail table and said third set of said plurality of event fields from said variable binding table to said process.

8. A method in accordance with claim 7, comprising:

storing at least one additional set of said plurality of event fields in a corresponding at least one additional report-ready tables, said at least one additional report-ready tables used by at least one report generator to generate at least one additional report, and said at least one additional set of said event fields respectively comprising each of said plurality of event fields that are required for generation of said respective at least one additional reports.

9. A method in accordance with claim 3, wherein:

said variable binding table comprises all of said event fields for a given event type that are not included in said detail table.

10. A method in accordance with claim 2, wherein:

said detail table comprises all of said event fields that are common to all of said event types.

11. A method in accordance with claim 1, comprising:

maintaining a count of a number of occurrences of events during a predetermined time interval of said event type of said event;

storing said count in an aggregation table.

12. A method in accordance with claim 1, comprising:

comparing said event to a pre-specified filter condition; and

discarding said event and not storing said event in said data warehouse if said event matches said pre-specified filter condition.

13. A method for retrieving a set of report fields from a network management system event data warehouse, said set of report fields for a given event stored in said data warehouse comprising a first set of a plurality of event fields that together comprise a network management system event, and said set of report fields being stored in a report-ready table that comprises each of said plurality of event fields that are essential for generation of a report, said method comprising:

receiving a network management system event, said network management system event comprising a plurality of event fields;

extracting at least a first set of said plurality of event fields from said network management system event;

storing said first set of said event fields in a report-ready table in a relational database, said report-ready table capable of storing multiple events and used by a report generator to generate a report, and said first set of said event fields comprising each of said plurality of event fields that are essential for generation of said report.

14. A method in accordance with claim 13, comprising:

receiving a report query from said report generator; and

sending said first set of said said plurality of event fields to said report generator.

15. A method in accordance with claim 13, comprising:

maintaining a count of a number of occurrences of events during a predetermnined time interval of said event type of said event;

storing said count in an aggregation table.

16. A data warehouse for storing network management system events, each of said events comprising one of a plurality of different event types, each of said network management system events comprising a plurality of event fields, said data warehouse comprising:

a plurality of related tables each associated with said event, said plurality of related tables comprising a report-ready event table comprising a first set of said plurality of event fields and stored in a relational database, said report-ready table capable of storing multiple events and used by a report generator to generate a report, and said first set of said event fields comprising each of said plurality of event fields that are essential for generation of said report.

17. A data warehouse in accordance with claim 16, comprising:

an export manager configured to receive said event, said export manager comprising formatting means for formatting a first set of said plurality of event fields into a report-ready table, said report-ready table defined according to a reporting type table class, said report-ready table class comprising each of said plurality of event fields that are essential for generation of said report; and

a communications interface for sending said report-ready event table to a data warehouse.

18. A data warehouse in accordance with claim 16, comprising:

an aggregation function which maintains an event count, said event count comprising a total number of occurrences of events of said event type of said event during a specified time interval.

19. A data warehouse in accordance with claim 16, comprising:

a filter function, said filter function creating a filter table specifying a condition;

wherein said export manager reads said condition, and is responsive to said condition to discard said event without storing said event in said data warehouse if said event matches said condition.

20. A data warehouse in accordance with claim 16, comprising:

a data retrieval interface for retrieving said first set of said plurality of events fields from said report-ready table.