Probe-Based QoS Message Filtering in UIM Hubs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Unified Infrastructure Management (UIM) systems lack the ability to filter Quality of Service (QoS) messages by origin, leading to overwhelming data pipelines for users who need to monitor specific components within the system, making it difficult to understand network performance and provide proactive support.
Innovation Solution
Deploying a probe within the UIM system to discover hubs, establish queues for logging QoS messages, and filter these messages based on specified criteria such as originating systems or generating probes, providing filtered information to a monitoring server for better component-level monitoring.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If all QoS messages are collected and logged without filtering, then complete data availability is achieved, but data pipeline complexity and user difficulty in finding relevant information increases
Solution Approach 1:
The probe performs preliminary filtering of QoS messages at the source before they enter the main data pipeline. By applying filter criteria to originate system, generating probe, or both, the system pre-processes data to remove irrelevant messages early, reducing downstream complexity while preserving all necessary information.
Solution Approach 2:
The probe acts as an intermediary component between the QoS message generation sources and the monitoring server. It mediates the data flow by selectively filtering messages based on configured criteria, thereby simplifying the overall data pipeline architecture while maintaining data completeness for relevant sources.
2Measurement precision
If filtering by multiple criteria is implemented, then monitoring precision for specific components is improved, but system complexity increases
Solution Approach 1:
The filtering system is designed to be dynamic and configurable, allowing users to adjust filter criteria based on monitoring needs. The probe can filter by originate system, generating probe, or both criteria simultaneously, providing flexible precision control without requiring a permanently complex system architecture.
Solution Approach 2:
The system changes filtering parameters dynamically based on user configuration. By adjusting which filter criteria are active (originate system, generating probe, or both), the system achieves varying levels of monitoring precision without permanently increasing complexity, as the same infrastructure adapts to different monitoring requirements.
3Loss of information
If comprehensive QoS monitoring of all components is performed, then complete system visibility is achieved, but ease of operation for users decreases
Solution Approach 1:
The probe extracts and removes irrelevant QoS messages from the data stream based on filter criteria. By taking out unwanted data at the source, the system maintains complete visibility of all components while presenting only relevant information to users, significantly improving ease of operation without sacrificing system-wide monitoring capability.
Solution Approach 2:
Relevant QoS messages are identified and prepared in advance through filtering before being presented to users. This preliminary action of selecting only pertinent data from the complete system view makes operation easier while ensuring no important system-wide information is lost, as the full dataset remains available but filtered for presentation.
Data Source
AI summary
Systems and methods may include deploying a probe within a unified infrastructure management (“UIM”) system. The systems and methods may include discovering, via the probe, hubs within the UIM system. Each hub may pass UIM traffic. The systems and methods may include establishing, for each hub, a queue on the hub. The queue may log quality of service (“QoS”) messages that pass through the hub. The systems and methods may include filtering, by the probe, each QoS message. The filtering of each QoS message may be filtering by a filter criteria. The filter criteria may specify an originating system at which the QoS message was originated. Additionally or alternatively, the filter criteria may specify a characteristic of a generating probe that generated the QoS message. The systems and methods may include providing information regarding each of the filtered QoS messages to a monitoring server.