Microservices Anomaly Detection via ML Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional approaches to managing microservices in complex IT systems are reactive and fail to predict or proactively handle issues, leading to outages and impacting performance and customer satisfaction.

Innovation Solution

A microservices anomaly detection and resolution platform that uses machine learning algorithms to analyze parameters and predict anomalous behavior, routing requests to secondary instances before issues occur, leveraging historical data and unsupervised learning models to identify deviations from normal operational patterns.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional reactive approaches are used to manage microservices, then system complexity is reduced, but reliability deteriorates due to inability to predict or handle issues in advance

Engineering Contradiction:
Improvemicroservice reliabilityVSAvoidanomaly detection platform complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by collecting parameters and analyzing microservice operations before anomalies occur. Machine learning models are trained on historical data to establish baseline behavior, enabling the system to detect and respond to deviations before they cause outages, thus improving reliability through proactive monitoring.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

An anomaly detection platform is introduced as an intermediary between microservice operations and system reliability. This platform collects parameters, analyzes operations using machine learning, and generates anomaly predictions, acting as a mediator that enhances reliability without requiring direct modification of microservice code.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If machine learning algorithms are used to analyze parameters and predict anomalies, then reliability is improved, but use of energy increases due to computational requirements

Engineering Contradiction:
Improveanomaly prediction accuracyVSAvoidcomputational energy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies partial action by selectively analyzing only those microservice operations that exhibit anomalous patterns rather than processing all operations uniformly. The machine learning models focus computational resources on detecting deviations from baseline behavior, reducing overall energy consumption while maintaining prediction accuracy.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The machine learning models are trained on historical microservice data to enable self-service anomaly detection. Once trained, the models automatically identify anomalies without requiring continuous human intervention or retraining, reducing the computational energy burden of manual monitoring while maintaining reliable predictions.

Inventive Principle:
Principle #25Self-service

3Reliability

If microservice requests are routed to secondary instances upon anomaly detection, then reliability is maintained, but device complexity increases due to routing infrastructure

Engineering Contradiction:
Improveservice continuityVSAvoidrouting system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The routing decision-making function is extracted from the anomaly detection platform and implemented as a separate, simple routing mechanism. When anomalies are detected, the system extracts affected microservice identifiers and routes requests to secondary instances using straightforward routing logic, reducing the complexity of the overall system while maintaining service continuity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Secondary microservice instances are created as copies of primary instances to handle request routing during anomalies. These copies maintain the same functional behavior but run on separate infrastructure, allowing requests to be redirected without modifying the original microservice code or complex routing logic.

Inventive Principle:
Principle #26Copying

4Productivity

If parameters are collected and analyzed in real-time using machine learning, then productivity is improved through proactive issue handling, but loss of time increases due to data processing requirements

Engineering Contradiction:
Improveproactive issue resolutionVSAvoidparameter analysis time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by continuously collecting and storing microservice parameters in advance of anomaly detection. Historical parameter data is pre-processed and stored in a structured format, enabling rapid analysis when anomalies occur without requiring real-time data gathering, thus reducing analysis time while maintaining proactive detection capabilities.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Manual parameter analysis is replaced with automated machine learning algorithms that process data efficiently. The machine learning models automatically analyze collected parameters, identify anomalies, and generate predictions without human intervention, reducing the time loss associated with manual monitoring while improving productivity through consistent, scalable analysis.

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

Data Source

PatentUS12019502B2Microservices anomaly detection
Publication Date: 2024.06.25 DELL PROD LP
  • US12019502B2 patent drawing
  • US12019502B2 patent drawing
  • US12019502B2 patent drawing

AI summary

A method comprises collecting parameters corresponding to at least one microservice operation processed by a first instance of a microservice, and analyzing the parameters using one or more machine learning algorithms. Based at least in part on the analyzing, a prediction is made whether the at least one microservice operation is anomalous. In the method, the first instance of the microservice is designated as being in an anomalous state responsive to predicting that the at least one microservice operation is anomalous. One or more microservice requests for the microservice are routed to a second instance of the microservice responsive to the anomalous state designation.