Event Message Priority Segmentation for Storage Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In large distributed computing systems, identifying and managing low-priority event messages is challenging due to the vast volume of data generated, leading to storage issues and the need to differentiate between relevant and superfluous messages.
Innovation Solution
Methods and systems are developed to identify low-priority event messages, allowing administrators to determine which can be deleted, sampled, or stored for specific periods, using event-type analysis and graphical user interfaces to manage storage requirements and retention times.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If all event messages are stored in event-log files, then complete information is preserved for analysis, but storage capacity is rapidly consumed and management complexity increases
Solution Approach 1:
The patent segments event messages into different priority levels (high-priority and low-priority) based on their importance for system monitoring and analysis. High-priority messages are retained in full while low-priority messages are subject to sampling or deletion, thus preserving critical information while reducing overall storage requirements
Solution Approach 2:
The patent changes the storage parameter for different types of event messages by applying different retention policies. High-priority messages receive full retention while low-priority messages receive reduced retention through sampling or deletion, optimizing the balance between information preservation and storage capacity
2Measurement precision
If all event messages are retained for analysis, then diagnostic accuracy is improved, but system management complexity increases
Solution Approach 1:
The patent segments event messages by priority level, allowing system administrators to focus on high-priority messages for detailed analysis while automatically managing low-priority messages through sampling or deletion policies, thereby reducing management complexity without sacrificing diagnostic accuracy for critical events
Solution Approach 2:
The patent applies different management parameters to different priority levels of event messages. High-priority messages are retained with full detail for accurate diagnosis, while low-priority messages are managed with simplified policies (sampling or deletion), reducing overall system management complexity
3Quantity of substance
If low-priority event messages are deleted, then storage capacity is optimized, but potential diagnostic information may be lost
Solution Approach 1:
The patent applies partial retention to low-priority event messages through sampling, where a subset of messages is retained while others are deleted. This partial action optimizes storage capacity while preserving enough diagnostic information to detect patterns or anomalies that might indicate underlying issues
Data Source
AI summary
Methods and systems to identify and respond to low-priority event messages are described. Methods identify types of event messages recorded in event-log files as low-priority event messages. Methods enable an information technology (“IT”) administrator, or other user, to determine which low-priority event messages may be deleted, how the low-priority event messages may be sampled for storage, or how long the low-priority event messages may be stored in a data-storage device.