Aggregate Activity Level Monitoring for Data Center Configuration Safety

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large computing systems with numerous components face challenges in managing configuration changes due to the complexity of interactions among components, making it difficult to determine whether the system is operating normally or abnormally, which can lead to unintended consequences during changes.

Innovation Solution

An activity level aggregator system that establishes a baseline aggregate activity level for the system, allowing for the comparison of current activity levels to determine if configuration changes are safe by focusing on the overall system's activity rather than individual component monitoring data, thereby facilitating informed decision-making.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If individual component monitoring data is collected and analyzed, then measurement precision of system state is improved, but device complexity and difficulty of detecting and measuring increase

Engineering Contradiction:
Improvesystem state detection accuracyVSAvoidmonitoring system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent combines monitoring data from multiple individual components into a single aggregate activity level metric. Instead of analyzing each component's monitoring data separately, the system merges them into one comprehensive indicator that reflects the overall system state, thereby maintaining measurement precision while reducing the complexity of data collection and analysis.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The aggregate activity level serves as a universal metric that can indicate the operational state of the entire computing system regardless of which specific components are involved. This single metric performs multiple functions: it detects system-wide abnormalities, triggers alerts, and provides a simplified view of system health without needing to analyze individual component data separately.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If configuration changes are made to improve system functionality, then adaptability and productivity are improved, but reliability may worsen due to unexpected consequences from component interactions

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system continuously monitors the aggregate activity level and uses this feedback to determine whether configuration changes should be permitted. Before allowing a configuration change, the system checks if the aggregate activity level indicates normal operation. This feedback mechanism ensures that changes are only made when the system is stable, thereby maintaining reliability while preserving configuration flexibility when conditions are appropriate.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs a preliminary check of the aggregate activity level before allowing configuration changes to proceed. By assessing the system state in advance and only permitting changes when the aggregate metric indicates normal operation, the system prevents changes that could exacerbate existing abnormalities, thus maintaining reliability while enabling adaptability when safe.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If aggregate activity level is used to assess system state, then ease of operation is improved, but measurement precision of individual component status may worsen

Engineering Contradiction:
Improvesystem state assessment simplicityVSAvoidindividual component status accuracy
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The system segments the overall system state assessment into two levels: an aggregate level for overall system health monitoring and an individual component level for detailed status information. The aggregate activity level provides a simplified view for operational decisions, while individual component monitoring data remains available when detailed diagnosis is needed, thus balancing ease of operation with measurement precision through hierarchical segmentation.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9225608B1Evaluating configuration changes based on aggregate activity level
Publication Date: 2015.12.29 AMAZON TECH INC
  • US9225608B1 patent drawing
  • US9225608B1 patent drawing
  • US9225608B1 patent drawing

AI summary

Disclosed are various embodiments for computing and using an aggregate activity level for a computing system. Activity level metrics are obtained from a corresponding plurality of components in a data center. A current aggregate activity level request is received. An aggregate activity level is computed from the activity level metrics. The aggregate activity level is compared to a baseline aggregate activity level. In response to the request, an indication is provided as to whether the aggregate activity level falls within a predefined range of the baseline aggregate activity level.