Intelligent Configuration Management via Threshold-Based Incident Reporting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data collection methods for application performance and incident alerts in IT environments are often siloed, lacking depth and utility for effective configuration management of user devices, which hinders IT administrators' ability to manage updates and maintenance operations efficiently.

Innovation Solution

The solution involves receiving application performance data and incident alerts across multiple tenant environments, using AI to determine if a threshold is met, and requesting incident reports from a subset of environments to generate an incident assessment, thereby improving configuration management by integrating asset intelligence and leveraging existing tools to capture intent data and rich data for better decision-making.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If data collection is performed across all tenant environments to ensure comprehensive application performance monitoring, then measurement precision is improved, but network burden and data transmission time increase

Engineering Contradiction:
Improveapplication performance monitoring accuracyVSAvoiddata transmission time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system requests incident reports from only a subset of tenant environments (third plurality) rather than all environments, based on whether incident alert thresholds are met. This partial data collection approach maintains measurement precision for critical incidents while reducing overall network burden and data transmission time.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The data collection process is segmented into multiple stages: first collecting application performance data from all environments, then collecting incident alerts from a second plurality, and finally requesting detailed incident reports only from a third plurality of environments where thresholds are met. This segmentation reduces total data transmission while maintaining monitoring accuracy.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If incident reports are requested from all tenant environments to ensure complete incident assessment, then information completeness is improved, but network burden and data processing complexity increase

Engineering Contradiction:
Improveincident assessment completenessVSAvoiddata processing complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system requests incident reports from only a third plurality of tenant environments that has a smaller count than the second plurality, based on threshold evaluations. This ensures incident assessment completeness for critical issues while reducing network burden and data processing complexity by excluding environments that did not trigger incident alerts.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of information

If comprehensive data collection from all tenant environments is performed, then configuration management utility is improved, but network burden and resource consumption increase

Engineering Contradiction:
Improveconfiguration management information completenessVSAvoidnetwork resource consumption
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The data collection process is divided into hierarchical stages: application performance data from first plurality of environments, incident alerts from second plurality, and detailed incident reports from third plurality. This segmentation reduces network resource consumption while maintaining configuration management information completeness through selective data gathering.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs partial data collection by requesting incident reports only from a subset of environments (third plurality) where incident thresholds are met, rather than from all environments. This reduces network resource consumption while maintaining sufficient information completeness for effective configuration management.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10853215B2Intelligent configuration management of user devices
Publication Date: 2020.12.01 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10853215B2 patent drawing
  • US10853215B2 patent drawing
  • US10853215B2 patent drawing

AI summary

A solution is disclosed for intelligent configuration management of user devices that includes: receiving application performance data for a plurality of applications from each of a first plurality of tenant environments or cloud services or both, the application performance data including a program ID for at least one application of the plurality of applications; receiving incident alerts related to the first program ID from each of a second plurality of tenant environments; based at least on receiving the incident alerts, determining whether a count of the second plurality of tenant environments meets a threshold; and based at least on the count of the second plurality of tenant environments meeting the threshold, requesting incident reports related to the program ID from each of a third plurality of tenant environments, wherein the third plurality of tenant environments has a smaller count than the count of the second plurality of tenant environments.