Event Classification for Root Cause Isolation in Cross-Domain Systems

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In cross-domain computing environments, identifying the root causes of events is complex and difficult due to the involvement of multiple configuration items from different domains, making it challenging to resolve issues effectively.

Innovation Solution

A configuration management system that utilizes event classification and type designation to identify configuration items and metrics, facilitating the isolation of root causes by using an event classification repository, metric acquisition module, and event response module to analyze and respond to events, thereby simplifying the identification and remediation of problems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple configuration items from different domains are monitored in cross-domain computing environments, then the system can detect more comprehensive events, but identifying the root causes becomes extremely complex and difficult

Engineering Contradiction:

Improveevent detection comprehensivenessVSAvoidroot cause identification complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the complex root cause identification process by introducing event classification that divides events into distinct categories (e.g., network events, storage events, compute events). This segmentation allows the system to handle different event types through domain-specific workflows rather than treating all events uniformly, thereby reducing the complexity of root cause identification while maintaining comprehensive monitoring across multiple domains.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an event classification repository and classification mechanism as an intermediary layer between event detection and root cause analysis. This intermediary categorizes events before they are analyzed, enabling the system to route different event types to appropriate handling procedures. The classification acts as a mediator that simplifies the path from comprehensive event monitoring to targeted root cause identification.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If comprehensive monitoring of configuration items across multiple domains is implemented, then more events can be detected, but the time and resources required to resolve events increase significantly

Engineering Contradiction:

Improveevent detection capabilityVSAvoidevent resolution time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary action by classifying events into categories before root cause analysis begins. The event classification repository pre-organizes event types and their associated workflows, so when an event is detected, the system can immediately retrieve the appropriate classification and follow the predefined resolution path. This preliminary classification eliminates the need to analyze all possible root causes for every event, significantly reducing resolution time while maintaining comprehensive monitoring.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent applies local quality by providing different analysis workflows and depth levels for different event categories. Rather than applying a uniform complex analysis to all events, the system tailors the root cause identification process to the specific event type - simple events receive streamlined handling while complex events get more thorough analysis. This localized approach reduces average resolution time while maintaining reliability for critical events.

Inventive Principle:

Principle #3Local quality

3Productivity

If event classification and metric acquisition modules are added to the system, then root causes can be isolated more efficiently, but the device complexity increases

Engineering Contradiction:

Improveroot cause isolation efficiencyVSAvoidsystem structure complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent implements universality by designing the event classification repository and classification modules to handle multiple event types across different domains through a unified framework. The same classification infrastructure serves network events, storage events, compute events, and other domain-specific events. This multi-functional approach improves root cause isolation efficiency across all domains while avoiding the need for separate complex systems for each event type, thereby limiting the increase in overall device complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9229898B2Causation isolation using a configuration item metric identified based on event classification

Publication Date: 2016.01.05 MICRO FOCUS LLC

AI summary

Based on an event classification for an event of a cross-domain computing environment, a metric of a configuration item is obtained and used to isolate a causation of the event, wherein the event is a symptom or occurrence of an operational problem of at least one computing device in the cross-domain computing environment.