Apparatus and method for capturing knowledge through an expert interface

• US 7,028,221 B2
• Filed: 05/21/2002
• Issued: 04/11/2006
• Est. Priority Date: 05/10/2001
• Status: Expired due to Fees

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Holland, Paul Edward, McDowell, Mark William, Carr, Adam Michael
• Primary Examiner(s): Knight, Anthony
• Assistant Examiner(s): Bell, Meltin
• Application Number:
  US10/152,556
• Publication Number:
  US 20020169734A1
• Time in Patent Office: 1,421 Days
• Field of Search: 706/60, 706/59
• US Class Current: 714/31
• CPC Class Codes: G06Q 10/04 Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem" market predictions or forecasting for commercial activities G06Q30/0202
• CPC Class Codes: Y10S 706/922 Computer program preparation

Abstract

An apparatus and method is provided for auditing the configuration of an enterprise comprising the steps of: collecting information relating to the configuration of the enterprise, analyzing the configuration information based on expert knowledge; and providing the result of the analysis in the form of reports, and other results of the analyses.

Claims

1. A method of creating and then utilizing one or more analyzers that can identify issues arising in the nodes of an enterprise having data collectors comprising the steps of:

for each analyzer that is to be created,

creating analyzer computer executable code that directs a computer to accept input data, to perform computations on the input data to detect the presence of one or more issues, and to output identifiers of any of the issues which are found to be present,

creating one or more machine-readable issue templates separate from the analyzer code and not computer executable corresponding to each of the one or more issue identifiers and each defining an issue report corresponding to an issue, and

creating a machine-readable descriptor of the analyzer separate from the analyzer code and not computer executable identifying the collector types whose output the analyzer code is intended to cause the computer to accept as input data;

collecting the created elements of each analyzer into an analyzer database; and

using a computer having access to the analyzer database and also to collector data gathered or obtainable from one or more nodes, for each of the nodes and for each of one or more of the analyzers, operating the computer under the control of the analyzer such that

the analyzer'"'"'s descriptor and its specification of collector types guides the computer in the automatic selection of input data from the node'"'"'s collector data,

the computer executes the analyzer'"'"'s computer executable code against this selected input data, and

if such execution outputs issue identifiers, the issue templates corresponding to the issue types outputted guide the computer in the automatic generation of issue reports.

2. A method in accordance with claim 1 wherein the step of creating an issue template includes the step of providing for the inclusion in at least one issue report the identity of a particular node where the issue is present.

3. A method in accordance with claim 2 wherein the step of creating an issue template includes the step of creating within at least one issue template a position marker indicating where the identity of a particular node is to be placed within the issue report.

4. A method in accordance with claim 1 wherein at least some of the analyzer code is written in Java and/or an equivalent architecture independent language.

5. A method in accordance with claim 4 wherein at least some of the analyzer code is written in C and/or C++ and/or in an equivalent conventional language.

6. A method in accordance with claim 5 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

7. A method in accordance with claim 4 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

8. A method in accordance with claim 1 wherein at least some of the analyzer code is written in C and/or C++ and/or an equivalent conventional language.

9. A method in accordance with claim 8 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

10. A method in accordance with claim 1 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

11. A method in accordance with claim 1 wherein the output data is presented in XML or an equivalent data base compatible web page format.

12. A method in accordance with claim 1 wherein the descriptor is presented in XML or an equivalent data base compatible web page format.

13. A system for detecting issues arising on the nodes of an enterprise having data collectors comprising:

one or more analyzer programs that accept data from one or more collector types, that perform computations to detect the presence of issues, and that output identifiers of issues which are present;

for each issue identifier, an issue report template;

for each analyzer program, a descriptor identifying the collector types whose data the analyzer requires;

an analyzer harness that can exercise a set of one or more analyzer programs against data gathered from a different node or set of nodes during each such exercise, providing each analyzer program with collector data designated by the analyzer'"'"'s descriptor and gathered from the node or set of nodes under examination; and

the analyzer harness responding to the output of issue identifiers by presenting reports formed in accordance with each issue identifier'"'"'s issue report template.

14. A system in accordance with claim 13 wherein the analyzer harness augments at least some issue reports with the identity of the particular node or set of nodes where the analyzer has determined the identified issue is present.

15. A system in accordance with claim 14 wherein the issue report templates for at least some issue identifiers contain an indication of the position within an issue report where the analyzer harness is to insert the identity of the particular node or set of nodes where the analyzer has determined the identified issue is present.

16. A system in accordance with claim 13 wherein at least some of the analyzer code is written in Java and/or an equivalent architecture independent language.

17. A system in accordance with claim 16 wherein at least some of the analyzer code is written in C and/or C++ and/or in an equivalent conventional language.

18. A system in accordance with claim 17 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

19. A system in accordance with claim 16 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

20. A system in accordance with claim 13 wherein at least some of the analyzer code is written in C and/or C++ and/or an equivalent conventional language.

21. A system in accordance with claim 20 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

22. A system in accordance with claim 13 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

23. A system in accordance with claim 13 wherein the output data is presented in XML or an equivalent data-base compatible web page format.

24. A system in accordance with claim 13 wherein the descriptor is written in XML or an equivalent data-base compatible web page format.

25. A computer-implemented method of identifying the presence of issues through the analysis of output data provided by collectors monitoring the nodes of an enterprises, comprising the steps of:

providing analyzer programs that define the steps of accepting data from one or more collector types, performing computations to detect the presence of issues, and that output identifiers of any issues which are present;

for each issue output identifier, providing an issue template that defines an issue report for that issue;

for each analyzer program, providing a descriptor identifying the collector types whose data the analyzer requires as its input; and

repeatedly exercising a set of the analyzer programs against output data gathered from different nodes or sets of nodes, providing each analyzer program with data from the types of collectors designated by the program'"'"'s descriptor; and

when issue identifiers are generated, generating an issue report guided by the corresponding issue template.

26. A method in accordance with claim 25 further including the step of inserting the node identity of the node or set of nodes where an issue arose into at least some of generated issue reports.

27. A method in accordance with claim 26 which includes, in the step of providing the issue templates for at least some issues, the step of indicating within the issue template where the identity of the node or set of nodes under analysis may be inserted.

28. A method in accordance with claim 25 wherein at least some of the analyzer code is written in Java and/or an equivalent architecture independent language.

29. A method in accordance with claim 28 wherein at least some of the analyzer code is written in C and/or C++ and/or in an equivalent conventional language.

30. A method in accordance with claim 29 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

31. A method in accordance with claim 28 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

32. A method in accordance with claim 25 wherein at least some of the analyzer code is written in C and/or C++ and/or an equivalent conventional language.

33. A method in accordance with claim 32 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

34. A method in accordance with claim 25 wherein at least some of the analyzer code is written in perl and/or kshell and/or an equivalent operating system shell language.

35. A method in accordance with claim 25 wherein the output data is presented in XML or an equivalent data-base compatible web page format.

36. A method in accordance with claim 25 wherein the descriptors are presented in XML or an equivalent data-base compatible web page format.

37. A system for detecting issues arising on the nodes of an enterprise having data collector means for collecting enterprise state data comprising:

one or more analyzer means for accepting data from one or more collector means, for performing computations to detect the presence of issues, and for outputting identifiers of issues which are present;

for each issue identifier, issue report template means for defining the structure of an issue report;

for each analyzer means, descriptor means for identifying at least the type of collector moans whose data the analyzer means requires;

analyzer harness means for exercising a set of one or more analyzer means against data gathered from a different node or set of nodes during each such exercise, for providing each analyzer mean'"'"'s with data from collector means designated by the analyzer means descriptor means and gathered from the node or set of nodes under examination; and

the analyzer harness means including means for responding to the output of issue identifiers by presenting reports formed in accordance with each issue identifier'"'"'s issue report template means.