Centralized Tracing Server for Distributed Compute Nodes

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current tracing technologies are inadequate for performing end-to-end tracing across multiple compute nodes, as they lack a centralized mechanism to initiate and manage tracing sessions effectively, making it difficult to diagnose issues that span multiple nodes.

Innovation Solution

A method and system for end-to-end tracing that involves a tracing server node connected to compute nodes, which receives requests for tracing sessions, initiates tracing on compute nodes by sending arguments to providers, receives and combines event reports, and sends tracing information back to the user node, allowing for centralized management of tracing across multiple nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If distributed tracing is performed across multiple compute nodes without centralized management, then tracing can be performed on individual nodes, but end-to-end tracing across multiple nodes cannot be achieved

Engineering Contradiction:

Improveend-to-end tracing capabilityVSAvoidtracing session management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

A tracing server acts as an intermediary between user nodes and compute nodes. The tracing server receives tracing session requests, manages session state, coordinates tracing across multiple compute nodes, and consolidates results. This mediator approach enables end-to-end tracing without requiring complex peer-to-peer coordination between distributed nodes.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple providers are deployed across distributed compute nodes, then tracing coverage is improved, but coordination and data consolidation become more difficult

Engineering Contradiction:

Improvetracing coverageVSAvoidtracing data consolidation

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The tracing server merges and consolidates tracing data from multiple distributed providers into a unified tracing session result. Event reports from different compute nodes are collected, correlated using session identifiers, and combined into coherent end-to-end trace information that presents a unified view of distributed system behavior.

Inventive Principle:

Principle #5Merging (Combining)

3Reliability

If centralized tracing management is implemented, then end-to-end tracing across multiple nodes is enabled, but system architecture complexity increases

Engineering Contradiction:

Improvediagnostic capabilityVSAvoidsystem architecture

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The tracing server performs multiple functions: receiving tracing requests, managing session state, coordinating with multiple compute nodes, collecting event reports, and generating consolidated results. This multi-functional approach enables comprehensive end-to-end tracing capability while centralizing complexity in a single manageable component rather than distributing it across all nodes.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10567250B2End-to-end tracing providers and session management

Publication Date: 2020.02.18 ORACLE INT CORP

AI summary

A method for end-to-end tracing includes receiving, from a user node, a request for a tracing session, receiving an argument and a provider identifier for the tracing session, and initiating tracing on compute nodes by sending the argument to a provider identified by the provider identifier, the provider located on each of the compute nodes. The method further includes receiving event reports from the compute nodes, and combining the event reports into a tracing information for the tracing session. The method further includes sending the tracing information to the user node.