Matchmaking-Based Debugging for Microservices Telemetry

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

As microservices architectures transition to using disaggregated computing resources, the volume of data collected for trace and performance telemetry becomes burdensome, especially in real-time interpretation, and poses challenges for networking due to high data transmission volumes in short periods.

Innovation Solution

Implementing a matchmaking-based enhanced debugging approach that utilizes sidecars for each microservice to enable distributed tracing as a streaming service, with anomaly detection and enhanced debug/tracing components that perform matchmaking on collected debug data, introducing timestamped markers and tags to facilitate global collection and analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If distributed tracing is implemented to monitor microservices in disaggregated computing environments, then system observability and debugging capability are improved, but data volume and networking burden increase significantly

Engineering Contradiction:
Improvesystem observabilityVSAvoiddata volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts and filters only the most relevant telemetry data points from the massive data stream generated by distributed tracing. The system identifies and extracts key metrics related to anomalies while discarding redundant information, thereby maintaining observability while reducing data volume burden on networking infrastructure.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the tracing system into multiple components: sidecar proxies at each microservice, collection agents, and analysis services. This segmentation allows distributed tracing to be implemented in a scalable manner where data is collected, filtered, and processed in stages, reducing the overall networking burden while maintaining comprehensive observability.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If comprehensive telemetry data is collected for debugging, then analysis completeness is improved, but real-time interpretation becomes burdensome

Engineering Contradiction:
Improveanalysis completenessVSAvoidreal-time interpretation speed
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent performs preliminary filtering, aggregation, and prioritization of telemetry data before it reaches the analysis stage. By pre-processing data to identify anomalies and extract relevant metrics in advance, the system ensures that when real-time interpretation is needed, the data is already organized and ready for rapid analysis, maintaining both completeness and speed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where the system continuously monitors telemetry data and adjusts its collection and filtering parameters based on observed patterns and anomalies. This feedback loop ensures that the most relevant data is prioritized for real-time interpretation while maintaining comprehensive analysis capabilities.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If debug mode is enabled to capture detailed tracing information, then debugging accuracy is improved, but data transmission volume increases

Engineering Contradiction:
Improvedebugging accuracyVSAvoiddata transmission volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The patent applies local quality by enabling detailed tracing and debugging information collection selectively at specific microservices or time periods when anomalies are detected, rather than uniformly across the entire system. This allows high-precision debugging where needed while reducing overall data transmission volume in normal operating conditions.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP4198739B1Matchmaking-based enhanced debugging for microservices architectures
Publication Date: 2025.06.11 INTEL CORP
  • EP4198739B1 patent drawingFigure 1
  • EP4198739B1 patent drawingFigure 2
  • EP4198739B1 patent drawingFigure 3

AI summary

An apparatus to facilitate matchmaking-based enhanced debugging for microservices architectures is disclosed. The apparatus includes one or more processors to: detect, by an anomaly detector in a sidecar of a microservice hosted by a container, an anomaly in telemetry data generated by the microservice, the microservice hosted in a container executed by the processor and part of a service of an application; enable, by an enhanced debug and trace component of the sidecar, a debug mode in the microservice, the debug mode based on a type of the anomaly; collect, by the enhanced debug and trace component, a target set of data points generated by the microservice; and process, by the enhanced debug and trace component, the target set of data points with a matchmaking process to generate a timestamp and a tag for a context for each data point of the target set of data points.