Asynchronous Handoff Identification in Distributed Web Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current application tracking tools fail to monitor multiple asynchronous requests effectively, providing an inadequate view of content page rendering and transactions in distributed web services, as they are designed to track only single content page backend transactions.
Innovation Solution
The system automatically detects and tracks asynchronous handoffs between threads and software components by instrumenting a virtual machine, such as a Java Virtual Machine (JVM), to identify and report monitoring information for overall transactions, including the original request and corresponding asynchronous requests, using thread handoff objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If current application tracking tools are used to monitor backend transactions, then single content page transactions can be tracked, but multiple asynchronous requests cannot be effectively monitored
Solution Approach 1:
The patent segments the monitoring system into multiple independent tracking components, each capable of handling specific asynchronous requests. The system divides the monitoring task by creating separate tracking instances for different thread handoffs and asynchronous operations, allowing each segment to monitor its specific transaction path independently while contributing to the overall transaction view.
Solution Approach 2:
The patent introduces thread handoff objects as intermediary elements that carry monitoring information between different threads and asynchronous operations. These objects act as mediators that preserve transaction context across thread boundaries, enabling the monitoring system to track asynchronous requests that would otherwise be invisible to traditional single-threaded monitoring approaches.
2Loss of information
If traditional monitoring systems track only single content page backend transactions, then system complexity remains low, but comprehensive view of distributed transactions is inadequate
Solution Approach 1:
The patent creates a universal monitoring framework that handles both synchronous and asynchronous transactions through a common architecture. The thread handoff objects and monitoring infrastructure are designed to be multi-functional, serving both traditional backend transaction monitoring and new asynchronous request tracking requirements through the same system components.
Solution Approach 2:
The patent implements a nested monitoring structure where thread handoff objects contain embedded monitoring data and context that is nested within larger transaction frameworks. This nesting allows monitoring information to be packaged at multiple levels - from individual asynchronous request context up to the overall distributed transaction view - without requiring separate independent systems for each level.
Data Source
AI summary
Asynchronous handoffs between threads and other software components may be automatically detected, and the corresponding working objects may be tracked. The system may report monitoring information for an overall transaction that includes the original request and corresponding asynchronous requests. Automatically detecting asynchronous requests may include instrumenting a virtual machine, such as a Java Virtual Machine (JVM), to detect the creation of thread handoff objects and the object and/or thread execution. Thread handoff objects may automatically tracked, tracked based on data learned over time, tracked based on user input, and otherwise configured. In some embodiments, after detecting the creation of a thread handoff object, an identification of the object of the call may be identified as being tracked in another server or application.