Monitoring Data Query Service With Source Precedence Rules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems require users to have detailed knowledge of data models and deployment of sensors across a computing infrastructure to retrieve monitoring data, making it complex and cumbersome to obtain and merge data from multiple sources.
Innovation Solution
A service that provides a flexible query interface to retrieve monitoring data across a computing infrastructure, hiding the complexity of data location and retrieval, and implementing precedence rules to determine the best data sources, allowing seamless access to both cloud and on-premises data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If users directly access monitoring data from multiple data sources, then data retrieval completeness is improved, but system complexity and operational difficulty increase
Solution Approach 1:
The patent introduces a service layer that acts as an intermediary between users and multiple data sources. This service receives user queries, automatically determines which data sources to access based on precedence rules, and merges results. Users interact only with the service interface without needing to know about underlying data source complexity, thus maintaining data retrieval completeness while significantly reducing operational difficulty.
Solution Approach 2:
The service provides a universal query interface that can access multiple types of data sources (cloud-based and on-premises) through a single standardized method. This multi-functional interface handles diverse data retrieval scenarios without requiring users to learn different access methods for different sources, improving ease of operation while maintaining comprehensive data access.
2Reliability
If users access data from both cloud and on-premises sources, then data availability is improved, but system complexity increases
Solution Approach 1:
The service layer mediates between users and heterogeneous data sources (cloud and on-premises). It implements precedence rules to determine which source to query first, automatically handling the complexity of multi-source access. This allows the system to maintain high data availability by querying multiple sources while hiding the complexity from users, who interact through a single unified interface.
Solution Approach 2:
The system segments data sources into different categories (cloud-based and on-premises) with defined precedence rules. The service processes queries by segmenting the access path according to these rules, querying higher-priority sources first before falling back to lower-priority ones. This segmentation manages system complexity by organizing multiple sources into a structured hierarchy while maintaining data availability.
3Loss of information
If manual data merging from multiple sources is implemented, then data completeness is improved, but time consumption increases
Solution Approach 1:
The service acts as an automated intermediary that performs data merging without user intervention. When a user submits a query, the service automatically determines which data sources to access, retrieves data from multiple sources according to precedence rules, and merges results into a unified response. This automation maintains data completeness while dramatically reducing time consumption compared to manual merging processes.
Solution Approach 2:
The service performs preliminary actions by pre-establishing precedence rules and data source hierarchies. When queries are received, the service has already determined the optimal access path and can efficiently retrieve and merge data without requiring users to manually plan or execute complex data gathering and merging operations, thus reducing time consumption while maintaining completeness.
Data Source
AI summary
A first facility may include a data source and an edge service. A second facility may include a first cloud service and a second cloud service. A request may be received at the first cloud service to onboard the data source. A command may be sent from the first cloud service to an edge service to onboard the data source. The edge service may configure the data source to provide monitoring data to the second cloud service through the edge service. A data query may be received at the second cloud service from a client. A set of data queries may be determined based on the data query. A response may be generated based on executing the set of data queries. The response may be provided to the client.