Configuration Tree Anomaly Detection for Conflicting Configurators
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The unintended overwriting of configuration settings by multiple configurators leads to undesired configuration states in managed entities, particularly in complex computer networks, which can disrupt network functionality and user experience.
Innovation Solution
Anomaly detection is implemented by annotating configuration trees with information identifying the configurator that modified each parameter, generating subtrees for each configurator, calculating weighted edit distances, and using a distance matrix to identify anomalous configurations, thereby alerting administrators to correct anomalies and prevent future disruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple configurators are allowed to configure a managed entity, then configuration flexibility and functionality are improved, but configuration conflicts and unintended overwriting occur
Solution Approach 1:
The system implements feedback by continuously monitoring configuration changes across multiple configurators and comparing them against a baseline configuration. When deviations are detected, the system generates alerts to notify administrators, creating a feedback loop that maintains configuration consistency while allowing multiple configurators to operate.
Solution Approach 2:
The patent introduces an intermediary anomaly detection system that sits between multiple configurators and the managed entity. This intermediary monitors and analyzes configuration changes, identifying anomalies before they cause conflicts, thereby mediating between the need for configuration flexibility and maintaining consistency.
2Adaptability or versatility
If multiple configurators modify managed entity settings, then system functionality is improved, but detection of configuration anomalies becomes more difficult
Solution Approach 1:
The system segments the configuration monitoring task by analyzing each configurator's changes independently against the baseline configuration. This segmentation allows the system to handle multiple configurators systematically, reducing the complexity of anomaly detection while maintaining comprehensive coverage.
Solution Approach 2:
The patent creates a copy of the baseline configuration and uses it for comparison against current configurations. This copying approach simplifies anomaly detection by providing a reference point, making it easier to identify deviations caused by multiple configurators without increasing detection complexity.
3Loss of information
If configuration changes are monitored and annotated, then configuration traceability is improved, but processing overhead increases
Solution Approach 1:
The system applies partial action by annotating and monitoring only those configuration parameters that deviate from the baseline, rather than tracking every single parameter. This selective approach improves traceability for critical changes while reducing unnecessary processing overhead for unchanged parameters.
Data Source
AI summary
Detecting an anomalous configurator of a plurality of managed entities. A plurality of configuration trees, each representing configuration parameters at a corresponding managed entity, include annotations that identify a configurator that configured each parameter. For a particular configurator, a plurality of subtrees is generated from the plurality of configuration trees. A set of weighted edit distances are calculated from the plurality of subtrees, each representing a degree of difference between a different pair of subtrees. A distance matrix is populated with the set of weighted edit distances, and the distance matrix is used to identify anomalous subtree(s) within the plurality of subtrees for the particular configurator. In embodiments, a configuration corresponding to an anomalous subtree considered to have been anomalously applied by the particular configurator. Data that identifies at least one managed entity associated with the anomalous subtree, and the particular configurator is stored.