Architecture-Aware Alert Enrichment for Microservices Workflows

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for managing production alerts in microservices architecture are inefficient, requiring manual intervention and deep knowledge of system architecture, and fail to automatically reflect changes in architectural states, leading to time-consuming and cumbersome alert management.

Innovation Solution

A method and system that utilizes a build time and runtime architecture digitizer to generate updated architecture models, map alerts to corresponding components, enrich alerts with relevant metrics, and provide correlation and severity scores to automate alert management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual intervention is used to manage production alerts, then deep knowledge of system architecture can be applied, but the process becomes time-consuming and cumbersome

Engineering Contradiction:
Improvealert management accuracyVSAvoidtime to resolve alerts
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically generating architecture diagrams from source code during the build process, and pre-establishing the relationship between architecture components and alert rules. This preliminary setup eliminates the need for manual architecture diagram creation and component mapping when alerts occur, reducing response time while maintaining accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by automatically updating architecture diagrams when code changes are detected, and autonomously mapping alert rules to relevant architecture components without requiring manual intervention. The system serves itself by continuously synchronizing the architecture model with the actual codebase and alert configurations.

Inventive Principle:
Principle #25Self-service

2Manufacturing precision

If manual updates are performed on architecture diagrams, then architectural accuracy can be maintained, but the process becomes extremely cumbersome for complex applications

Engineering Contradiction:
Improvearchitecture model accuracyVSAvoidspeed of architecture updates
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system replaces the manual mechanical process of updating architecture diagrams with an automated computational system. The build time architecture digitizer automatically generates and updates architecture diagrams by analyzing source code, replacing manual drawing and updating processes. This substitution maintains accuracy through systematic code analysis while dramatically improving productivity by eliminating manual effort.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system creates accurate copies of the actual system architecture by generating architecture diagrams that mirror the real codebase structure. The build time digitizer produces a digital copy of the architecture from source code, and the runtime digitizer updates this copy automatically when changes are detected, ensuring the diagram remains an accurate representation without manual intervention.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If architecture diagrams are updated manually for every code change, then the diagrams remain current, but the effort required increases significantly

Engineering Contradiction:
Improveresponsiveness to code changesVSAvoidcomplexity of update process
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements dynamics by making the architecture diagram updates automatic and continuous rather than static and manual. The runtime architecture digitizer continuously monitors for code changes and automatically updates the architecture diagram, creating a dynamic system that adapts to changes without requiring manual intervention. This dynamic approach maintains responsiveness while reducing complexity by eliminating the need for manual update processes.

Inventive Principle:
Principle #15Dynamics

4Extent of automation

If existing alert management solutions are used, then basic alert collection is possible, but automatic mapping of alerts to architecture components is not achieved

Engineering Contradiction:
Improveautomation of alert mappingVSAvoidcontext information in alerts
Core Design Contradiction:
Extent of automationVSLoss of information

Solution Approach 1:

The system merges previously separate processes into a unified automated workflow. The build time architecture digitizer generates architecture diagrams, the runtime digitizer monitors code changes, and the alert management system automatically maps alerts to architecture components by combining these functions. This merging achieves automatic alert mapping while preserving context information by integrating architecture awareness directly into the alert management process.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12511211B2Method and system for managing a set of alerts related to an application workflow
Publication Date: 2025.12.30 JPMORGAN CHASE BANK NA
  • US12511211B2 patent drawing
  • US12511211B2 patent drawing
  • US12511211B2 patent drawing

AI summary

A method and a system for managing a set of alerts related to an application workflow are disclosed. The method includes: detecting, by a processor via a build time architecture digitizer (BTAD), request for new infrastructure component provisioning; generating via BTAD, updated architecture model; monitoring, via runtime architecture digitizer (RAD), set of services related to new infrastructure component; generating, via RAD, final architecture model; receiving, at alert enricher module (AEM) from database, set of alerts; mapping, via AEM, alerts with corresponding components of final architecture model; assigning, via AEM, corresponding components from final architecture model to alerts; enriching, via AEM, alerts with relevant metrics and log details; generating, via AEM, set of enriched alerts; and providing, via AEM, enriched alerts to manage set of alerts.