Appeal 2007-0428
Application 10/210,361
recovery action is to be located. (Specification 13). Upon receiving the
identified incident, a log analysis engine (400, 530) compares the incident
against known incidents in the updated local cache (520) to locate directives
and hints associated with such known incidents. Then, the log analysis
engine (400, 530) forwards the collected directives3 to a diagnostic engine
(460), which in turn, executes the corresponding diagnostic modules (470,
472, 474) that provide a recovery action associated with the identified
incident. (Specification 11, 12).
Miller discloses a software-driven system for automatically detecting,
diagnosing and solving a problem. (Abstract). Miller’s system primarily
utilizes three components as part of the customer’s site software (61) to
automate the monitoring, diagnosing, and solution processes.4 First, it uses
a customer knowledge base (73) that stores logic to diagnose and solve each
particular problem. Second, it uses an engine (65) for managing the
execution code of the customer knowledge base to diagnose and solve each
particular problem. Last, it uses primitives (74) to generate an interface to
access the entries in the knowledge base. (Miller 13, ll. 12-19).
The customer knowledge database taught by Miller contains a plurality of
entries, each addressing a specific problem, and each entry having a four-
part executable code. (Id. 4, ll. 10-17). First, an initialization process
executes codes to a database entry with the customer site software. Second,
an immediate response process executes codes to cache locally a database
3 Appellant’s specification, at page 10, lines 27-28, defines a directive as the
dynamic tuning of information for incident handling.
4 Miller indicates that in lieu of an inference engine that provides solutions
to specific problems, the disclosed system uses a database containing entries
of very specific symptoms and solutions. (Miller 3, ll. 10-14).
4
Page: Previous 1 2 3 4 5 6 7 8 9 Next
Last modified: September 9, 2013