Node Hierarchy Impact Calculation for Computing Infrastructure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for monitoring the health and status of computing infrastructure resources are inefficient, as they often require evaluating all nodes during impact calculation, fail to recognize context-dependent impacts, and do not allow reconfiguration of resource relationships within service models, leading to sub-optimal impairment identification and maintenance.

Innovation Solution

A system and method that generate a node hierarchy based on configurable impact rules, allowing for parallel impact calculation across nodes affected by impairments, identifying both vertical and horizontal dependencies, and enabling reconfiguration of resource relationships within service models to accurately assess impairment severity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If all nodes are evaluated during impact calculation, then comprehensive impairment identification is achieved, but processing time and computational resources increase significantly

Engineering Contradiction:
Improveimpairment identification accuracyVSAvoidimpact calculation time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system segments the computing infrastructure into service models with hierarchical node structures. Instead of evaluating all nodes uniformly, impact calculation is segmented to only affect nodes within the same service model as the impaired resource. This segmentation maintains comprehensive impairment identification within relevant boundaries while eliminating unnecessary evaluations across the entire infrastructure, thus resolving the contradiction between accuracy and processing time.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by making impact calculation scope dependent on the specific service model context. Each service model has its own node hierarchy and impact relationships, allowing the system to apply impact calculation locally only where relevant rather than globally across all nodes. This ensures precise impairment identification within the affected service model while avoiding waste of computational resources on unrelated nodes.

Inventive Principle:
Principle #3Local quality

2Stability of the object's composition

If fixed resource relationships are maintained in service models, then system stability is preserved, but adaptability to reconfiguration needs is reduced

Engineering Contradiction:
Improveservice model structure stabilityVSAvoidresource relationship reconfiguration capability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system implements dynamics by allowing service model structures and resource relationships to be modified at runtime. The node hierarchy and impact relationships within service models are not fixed but can be reconfigured dynamically to adapt to changing infrastructure requirements. This dynamic capability enables the system to maintain stability through controlled changes while providing the adaptability needed for reconfiguration, resolving the contradiction between structural stability and flexibility.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11265203B2System and method for processing alerts indicative of conditions of a computing infrastructure
Publication Date: 2022.03.01 SERVICENOW INC
  • US11265203B2 patent drawing
  • US11265203B2 patent drawing
  • US11265203B2 patent drawing

AI summary

Systems and methods for processing alerts indicative of conditions of nodes of a computing infrastructure are herein disclosed as comprising, in an implementation, generating a node hierarchy comprising nodes associated with a service model, wherein relationships between the nodes are based on impact rules, identifying alerts related to the node hierarchy, wherein the alerts are indicative of impairments affecting at least a portion of the node hierarchy, and performing impact calculation for nodes of the node hierarchy based on the identified alerts. In an implementation, the impact values may be calculated in parallel for nodes indicated for processing. In an implementation, the nodes associated with the service model represent infrastructure or applicative resources and comprise nodes included in the service model and nodes related to, but not included in, the service model.