Transaction Stitching via Data Normalization Layer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing transaction monitoring systems struggle to provide a comprehensive, end-to-end view of transactions that traverse multiple application environments, as they lack integration capabilities to correlate and combine monitoring data across diverse platforms and systems.
Innovation Solution
The implementation of a data normalization layer with APIs that enable horizontal and vertical integration of monitoring agents, allowing for the association and correlation of transaction attributes across multiple application environments, thereby providing an end-to-end view of transactions through stitching and linking techniques.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If transaction monitoring is performed across multiple application environments using separate monitoring agents, then monitoring coverage is improved, but system complexity increases and end-to-end transaction correlation becomes difficult
Solution Approach 1:
The patent introduces a data normalization layer as an intermediary component that sits between multiple heterogeneous monitoring agents and the central monitoring system. This normalization layer translates and standardizes transaction attributes from different application environments into a unified format, enabling end-to-end transaction correlation without requiring direct integration between diverse monitoring systems. The normalization layer mediates the communication protocol and data structure differences, thus improving monitoring coverage while managing system complexity.
Solution Approach 2:
The patent implements a universal transaction attribute structure that can accommodate multiple types of application environments (mainframe, web, distributed systems) through a single standardized interface. The monitoring system uses universal identifiers and attribute formats that work across different platforms, allowing the same monitoring infrastructure to handle diverse transaction types without requiring platform-specific customization, thereby improving versatility while controlling complexity.
2Adaptability or versatility
If multiple monitoring agents are deployed across different platforms, then monitoring versatility is improved, but data correlation and stitching difficulty increases
Solution Approach 1:
The patent transforms transaction attributes from heterogeneous formats into a standardized parameter structure through the data normalization layer. By changing the parameter representation (identifiers, timestamps, transaction attributes) into a universal format, the system enables automatic correlation and stitching of transaction data across different platforms. The normalization process converts platform-specific parameter variations into consistent standardized parameters, making data correlation feasible despite monitoring versatility requirements.
3Loss of information
If comprehensive transaction attributes are collected from all application environments, then monitoring completeness is improved, but information processing complexity increases
Solution Approach 1:
The patent extracts only the essential transaction attributes needed for end-to-end monitoring and correlation through the data normalization layer. Rather than processing all available data from multiple application environments, the system identifies and extracts key identifiers, timestamps, and transaction attributes that are sufficient for stitching and correlation purposes. This selective extraction maintains monitoring completeness for critical transaction information while reducing information processing complexity by filtering out redundant or non-essential data.
Data Source
AI summary
A first transaction attribute is received from a first monitoring agent. The first transaction attribute includes a plurality of identifiers and is associated with a transaction. A second transaction attribute is received from a second monitoring agent. The second transaction attribute is associated with the transaction. The transaction is monitored through a plurality of application environments by associating at least a portion of the first transaction attribute with at least a portion of the second transaction attribute.