Trace Manager for Microservice Latency and Log Correlation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In microservice-based architectures, conventional tracing technologies face challenges in presenting a holistic view of latency issues and log information across distributed systems, making it difficult for developers to troubleshoot performance problems effectively.

Innovation Solution

A trace manager is implemented to analyze series of calls between applications, providing metrics like latency and start time, and presenting these in association with correlated log entries, with user interface features for selecting calls, displaying dependency graphs, and filtering logs based on HTTP requests, while handling multi-tenancy and access privileges.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If conventional tracing technology is used in microservice-based architectures, then tracing functionality can be provided across distributed systems, but it becomes difficult to present a holistic view of latency issues and log information across multiple microservices

Engineering Contradiction:

Improvetrace information completenessVSAvoidtroubleshooting difficulty

Core Design Contradiction:

Loss of informationVSEase of operation

Solution Approach 1:

The patent combines multiple trace information elements (latency metrics, log entries, call stack data, dependency graphs) into a single integrated view. The trace manager aggregates data from multiple microservices and presents them together in a unified interface, allowing developers to see the complete trace picture without switching between different tools or views.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The trace manager provides multiple functionalities in a single system: collecting trace data, analyzing latency metrics, correlating log entries, generating call stacks, creating dependency graphs, and managing user access privileges. This multi-functional approach replaces the need for multiple separate tracing tools.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If detailed trace information is collected across all microservices, then comprehensive troubleshooting data is available, but the complexity of managing and presenting this information increases

Engineering Contradiction:

Improvetroubleshooting accuracyVSAvoidtrace management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the complex trace information into organized components: latency metrics for each call, correlated log entries, call stack traces, and dependency graphs. Each segment is processed and presented separately but linked together, making the overall complex information manageable and understandable.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The trace manager acts as an intermediary between the complex distributed trace data and the developer. It collects, processes, correlates, and simplifies the raw trace information from multiple microservices, transforming it into a coherent presentation that reduces complexity while maintaining reliability.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Loss of information

If the trace manager provides access to all microservice logs, then complete trace visibility is achieved, but security requirements for managing user access privileges become more complex

Engineering Contradiction:

Improvetrace visibilityVSAvoidaccess control complexity

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The trace manager implements dynamic access control where user permissions are flexible and adaptable. The system can adjust what trace information each user can access based on their privileges, allowing complete visibility for authorized users while automatically restricting access for others. This dynamic permission system handles security requirements without manual configuration for each user.

Inventive Principle:

Principle #15Dynamics

4Device complexity

If latency metrics and logs are displayed separately, then data organization is simplified, but developers cannot easily correlate latency issues with specific log entries

Engineering Contradiction:

Improvedata presentation complexityVSAvoidissue correlation difficulty

Core Design Contradiction:

Device complexityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent merges latency metrics and log entries into a correlated display where each latency measurement is directly associated with its corresponding log entries. The trace manager presents them together in the same view, allowing developers to easily correlate performance issues with specific log events without switching between separate displays.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS10489285B2Trace management

Publication Date: 2019.11.26 VMWARE INC

AI summary

Systems, methods, and computer program products for trace management in a distributed computing environment are described. A trace manager receives a request to analyze a trace of a series of calls between applications serving requests in a microservice architecture. The trace manager determines metrics including, for example, latency information and start time for the series of calls. The trace manager presents the metrics in association with log entries correlated to the series of calls. A call stack, or one or more latency indicators, provides a user interface of selecting one or more calls. A user selection of a particular call in the call stack or a latency indicator causes one or more corresponding log entries to be emphasized or filtered. The call stack and the one or more latency indicators can have various display configurations.