Event Routing Table Threshold Filtering for Storage Clusters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing event notification systems, such as syslog, generate excessive duplicate notifications in storage system clusters, overwhelming administrators and failing to filter events effectively across multiple nodes, leading to irrelevant messages.
Innovation Solution
An event routing table stored in a replicated database across nodes in a storage system cluster, which sets threshold values to suppress repeated notifications based on occurrence and time, and maps user-defined destinations for targeted event notification delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional syslog program is used for event notification, then event notifications can be sent to administrators, but excessive duplicate notifications are generated that overwhelm administrators
Solution Approach 1:
The patent applies preliminary action by pre-configuring an event routing table with threshold values before events occur. The routing table stores destination information and threshold parameters (occurrence count and time interval) in advance, enabling the system to automatically filter duplicate notifications without requiring real-time complex processing when events are generated.
Solution Approach 2:
The event routing table serves as an intermediary between the event monitoring system and the notification delivery mechanism. It mediates the notification process by comparing incoming events against stored thresholds and destination rules, selectively forwarding only significant events while filtering out duplicates, thus resolving the contradiction between reliable notification and harmful duplication.
2Reliability
If syslog is configured to send all routine events to ensure notification of interesting events, then no important events are missed, but numerous unwanted event messages are received
Solution Approach 1:
The patent applies local quality by allowing different threshold configurations for different event types and destinations in the event routing table. Each routing entry can have customized occurrence thresholds and time intervals tailored to specific event categories and recipient preferences, enabling administrators to receive appropriate notification volumes for each event type without missing important occurrences.
Solution Approach 2:
The system changes parameters by dynamically adjusting notification delivery based on threshold parameters stored in the routing table. Instead of uniformly sending all events, the system modifies the notification behavior by comparing event characteristics against configurable thresholds (occurrence count, time intervals), thereby reducing notification volume while maintaining detection completeness for significant events.
3Device complexity
If syslog is limited to single node operation, then system complexity is reduced, but duplicate event notifications from clustered systems cannot be filtered
Solution Approach 1:
The event routing table provides universal functionality that works across single-node and multi-node clustered environments. The same routing table structure and threshold-based filtering mechanism handle events from any number of nodes, making the system universally applicable without requiring complex architecture-specific implementations while maintaining duplicate filtering capability.
Solution Approach 2:
The patent uses copying by replicating the event routing table across multiple nodes in a clustered system. Each node maintains a copy of the routing table with identical threshold configurations, enabling consistent duplicate event filtering across the cluster without requiring complex inter-node communication or centralized control, thus maintaining simplicity while gaining multi-node functionality.
Data Source
AI summary
A system and method efficiently conveys event notification using an event routing table. An event is detected and forwarded to an event management system (EMS) that determines if any thresholds have been exceeded. If a threshold has been exceeded, one or more destination names from a routing table are expanded using a destination table and appropriate event notifications are sent.