Automated Alert Management for Distributed Application Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing and recovering from hardware and software issues in distributed networked communication environments is costly and requires extensive manual intervention, as existing automated systems lack comprehensive automation and escalation processes.

Innovation Solution

Implementing an automated alert management system that maps detected issues to recovery actions, escalating unresolvable alerts to designated personnel while expanding an automated resolution knowledge base through a cyclical escalation method and recording information for future improvements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual management and recovery methods are used for distributed applications, then problems can be addressed with existing expertise, but the cost and resource requirements become prohibitive

Engineering Contradiction:
Improveproblem resolution capabilityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables automated self-service through the automation engine that independently detects alerts, maps them to recovery actions, executes remediation, and escalates only when necessary. This eliminates the need for continuous manual monitoring and intervention, reducing operational complexity while maintaining reliability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-mapping alerts to recovery actions in a knowledge base before problems occur. When alerts are detected, the corresponding remediation actions are already prepared and can be executed immediately, enabling rapid response without manual analysis or decision-making.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If automated recovery systems are implemented, then operational costs are reduced, but the system lacks comprehensive automation and escalation processes

Engineering Contradiction:
Improveautomation efficiencyVSAvoidautomation completeness
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The automation system is segmented into distinct functional components: alert detection, alert mapping to recovery actions, automated execution of remediation, and escalation to human operators when automation cannot resolve the issue. This segmentation allows comprehensive automation of routine tasks while preserving human intervention for complex problems, achieving both high automation efficiency and completeness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system incorporates feedback loops where the automation engine continuously monitors system state, evaluates the effectiveness of executed recovery actions, and adjusts its behavior accordingly. Escalation feedback from human operators is also fed back into the knowledge base to improve future automated responses, creating a self-improving automation system.

Inventive Principle:
Principle #23Feedback

3Loss of time

If comprehensive monitoring and automated response systems are deployed, then problem detection and resolution speed improves, but the system complexity and initial investment increase

Engineering Contradiction:
Improveproblem resolution timeVSAvoidsystem architecture complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The automation engine serves multiple functions: it detects alerts from various sources, maps them to appropriate recovery actions, executes remediation, and escalates when necessary. This multi-functional design consolidates what could be separate complex systems into a single unified platform, reducing overall system architecture complexity while maintaining fast problem resolution capabilities.

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

Solution Approach 2:

The knowledge base acts as an intermediary between alert detection and recovery action execution. It stores pre-defined mappings between alert types and remediation actions, allowing the automation engine to quickly resolve problems without complex real-time decision logic. This intermediary layer simplifies the system architecture by decoupling detection from response while enabling rapid automated resolution.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2561444B1Automated recovery and escalation in complex distributed applications
Publication Date: 2018.12.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP2561444B1 patent drawingFigure 1
  • EP2561444B1 patent drawingFigure 2
  • EP2561444B1 patent drawingFigure 3

AI summary

Alerts based on detected hardware and/or software problems in a complex distributed application environment are mapped to recovery actions for automatically resolving problems. Non-mapped alerts are escalated to designated individuals or teams through a cyclical escalation method that includes a confirmation hand-off notice from the designated individual or team. Information collected for each alert as well as solutions through the escalation process may be recorded for expanding the automated resolution knowledge base.