Middleware Message Queue Transaction Tracking via Activity Trace Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Middleware message queues do not expose necessary data for complete and efficient transaction tracking, leading to performance issues, accuracy problems, and inability to dynamically enable/disable data collection due to incomplete data.
Innovation Solution
The approach detects inbound and outbound messages in a middleware message queuing platform, retrieves activity trace data, and generates event records to build transaction flow topologies and report performance metrics by utilizing the platform's maintained activity trace data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional transaction tracking agents construct complete transaction tracking data from multiple inter-dependent monitoring points, then transaction tracking coverage is improved, but system performance deteriorates and data collection cannot be dynamically enabled/disabled
Solution Approach 1:
The patent extracts the necessary transaction tracking data directly from the message queue platform's existing activity trace data, rather than collecting data from multiple monitoring points. This extraction approach obtains complete transaction tracking information (message IDs, timestamps, queue names, application names) from a single source, eliminating the need for multiple instrumentation points and improving system performance while maintaining tracking completeness.
2Measurement precision
If multiple instrumentation points are required for transaction tracking, then transaction tracking accuracy is improved, but device complexity increases
Solution Approach 1:
The patent leverages the message queue platform's existing activity trace data infrastructure to serve multiple purposes: both operational monitoring and transaction tracking. By making the activity trace data accessible and complete, the same data source fulfills both the platform's operational needs and the transaction tracking requirements, eliminating the need for separate monitoring infrastructure and reducing overall system complexity.
3Productivity
If middleware message queues expose complete activity trace data, then transaction tracking efficiency is improved, but data security and privacy concerns worsen
Solution Approach 1:
The patent applies local quality by exposing activity trace data with appropriate levels of detail based on the specific transaction tracking needs. Rather than exposing all possible data globally, the solution provides the specific fields required for transaction tracking (message IDs, timestamps, queue names, application names) while maintaining the security model and access controls of the underlying message queue platform, thus balancing efficiency with security.
Data Source
AI summary
An approach is provided that detects inbound messages being put to message queues managed by a middleware message queuing platform. The approach retrieves activity trace data corresponding to each of the inbound messages, with the activity trace data maintained by the middleware message queuing platform. The approach generates inbound event records corresponding the inbound messages based on the activity trace data. The approach then detects outbound messages retrieved from the message queues. Activity trace data corresponding to the outbound messages is retrieved and the approach generates an outbound event record for each outbound message. The approach receives a transaction request from a requestor that corresponds to a message. The approach retrieves and returns the inbound event records and outbound event records that correspond to the requested message. The retrieved event records are used for transaction tracking: to build transaction flow topologies and to report transaction performance metrics.