Event Database for Cloud Fault Localization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud computing, when faults occur, operation and maintenance personnel face inefficiencies due to scattered information and the lack of automated mechanisms for synchronizing data, leading to labor-intensive and time-consuming fault localization.
Innovation Solution
A method and apparatus that summarize and associate event information in an event database, allowing for quick querying of events by machine name and time, enabling efficient fault localization by outputting relevant information in a structured manner.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual communication and tracking is used for fault localization, then personnel can communicate tracing progress, but efficiency is low and time consumption is high
Solution Approach 1:
The system enables automated fault localization through self-service mechanisms where the event database automatically collects, stores, and queries event information without manual intervention. The system autonomously synchronizes information between services and presents relevant events to operators, eliminating the need for manual tracking and communication while improving efficiency and reducing time consumption.
2Loss of information
If information is scattered in different places without synchronization mechanism, then each service maintains its data, but information cannot be quickly acquired and additional labor is required
Solution Approach 1:
The patent merges scattered event information from multiple services into a unified event database. The database collects event information including event start time, event end time, machine name, and event content from different sources and stores them in a centralized location, enabling quick acquisition and eliminating the need for manual information gathering across multiple systems.
Solution Approach 2:
The event database serves as a universal information repository that handles multiple functions: collecting events from various services, storing standardized event data, querying events by multiple criteria (machine name, time range, event type), and presenting information in a unified format. This multi-functional system replaces multiple separate information sources and simplifies access.
3Loss of time
If automated means are introduced for information synchronization, then positioning time is reduced, but system complexity increases
Solution Approach 1:
The system performs preliminary actions by pre-collecting and pre-storing event information in the event database before faults occur. Event data including start time, end time, machine name, and content are continuously gathered and organized in advance, so when a fault occurs, the information is already prepared and can be quickly queried without complex real-time synchronization operations.
Data Source
AI summary
Embodiments of the present disclosure provide a method and apparatus for outputting information. The method includes: summarizing event information into an event database in response to receiving the event information, where the event information includes an event start time, an event end time, a machine name, and an event content; associating and storing event information of a same machine name; querying an event database for event information including a target machine name and an event end time greater than or equal to a predetermined time before a current time and an event start time less than or equal to the current time, in response to receiving a query request including the target machine name; and outputting queried event information.