Global Event Log for Multi-Layer Software System Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex software systems with multiple layers and distributed processing make it difficult to assess system resource utilization during service requests, as existing technologies lack a comprehensive method for logging and analyzing event flows across all layers.
Innovation Solution
A method and apparatus that utilize a global event log to accumulate entries of events across multiple software layers, with an event trace facility providing a sequence of these entries in a tree structure or time sequential order through a graphical user interface, managed by a log manager to track system resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If a global event log accumulates entries from multiple software layers, then measurement precision of system resource utilization is improved, but device complexity increases
Solution Approach 1:
The logging system is segmented into distinct functional modules: a log manager that controls log operations, an event trace facility that retrieves and processes log data, and a graphical user interface that presents information to users. This segmentation allows each component to specialize in specific tasks, improving measurement precision while managing complexity through modular design.
Solution Approach 2:
The event trace facility acts as an intermediary between the global event log and the graphical user interface. It retrieves log entries, processes them into meaningful sequences, and presents them in organized formats (tree structure or time sequential order), thereby enabling precise resource utilization assessment without exposing the underlying logging system complexity to end users.
2Loss of information
If event entries are tracked across multiple software layers, then information completeness is improved, but difficulty of detecting and measuring increases
Solution Approach 1:
The global event log is designed as a universal logging mechanism that captures events from multiple software layers (application layer, operating system layer, hardware layer) through a standardized interface. Each log entry contains universal fields such as timestamps, event identifiers, and resource identifiers, enabling complete event flow tracking across heterogeneous layers while simplifying detection and measurement through consistent data structures.
Solution Approach 2:
The system implements feedback mechanisms where the graphical user interface allows users to query the event trace facility for specific service requests, and the facility retrieves relevant log entries and presents them in organized formats. This feedback loop enables complete information retrieval while reducing analysis difficulty through automated processing and structured presentation of multi-layer event data.
3Ease of operation
If a graphical user interface presents event sequences, then ease of operation is improved, but device complexity increases
Solution Approach 1:
The graphical user interface presents simplified copies or representations of the complex event log data. Instead of displaying raw log entries directly, the system creates processed views such as tree structures showing hierarchical event relationships or time-sequential orders showing chronological progression. These copied representations maintain the essential information needed for resource utilization assessment while dramatically improving ease of operation.
Data Source
AI summary
Method and apparatus for logging and analyzing event flows associated with execution of a service request in a software system, such as a computer-based system comprising a multi-disc data storage array. Execution of the service request results in a plurality of events carried out by multiple layers of the software system. A global event log accumulates a corresponding plurality of entries which associates each of the events carried out by the multiple layers. An event trace facility preferably accesses the global event log to provide a sequence of the entries corresponding to the service request, such as in a tree structure or time sequence order displayed by a graphical user interface. A log manager preferably controls operation of the global event log. Entries in the global event log are preferably entered sequentially for each ongoing process, and each entry preferably includes an identifier that identifies the associated service request.