Event Documentation System for Transaction Performance Measurement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computer systems face challenges in measuring the duration of processing phases across complex business processes involving multiple documents and disparate components, requiring extensive modifications that can impact system performance.
Innovation Solution
A method and system for documenting events in a computer system that involves receiving event information, identifying an anchor step type, and associating it with time-of-occurrence information in an execution log to evaluate performance measures, allowing for flexible definition and tracking of key performance indicators across various transaction processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If system components continuously report detailed information to pinpoint event occurrence, then measurement precision is improved, but device complexity increases and system performance is affected
Solution Approach 1:
The patent extracts the event timing documentation function from individual application programs and centralizes it in a separate timestamp service. Application programs only need to log events with basic information, while the timestamp service independently retrieves execution log data and calculates precise timestamps. This separation reduces application program complexity while maintaining high measurement precision.
Solution Approach 2:
The timestamp service acts as an intermediary between application programs and the execution log. Instead of application programs directly querying and analyzing execution logs (which would increase their complexity), the timestamp service mediates by automatically retrieving log data, matching events with their timestamps, and providing processed timing information to applications.
2Measurement precision
If system components are extensively modified to track events, then measurement precision is improved, but productivity decreases
Solution Approach 1:
The system performs preliminary actions by maintaining execution logs that automatically record all transaction steps as they occur. These logs are prepared in advance with complete transaction data, so when event timing analysis is needed, the timestamp service can immediately retrieve and process the pre-existing log data without interrupting or slowing down the original transaction processing.
Solution Approach 2:
The timestamp service creates a copy of the execution log data specifically for timing analysis purposes. Instead of modifying the original transaction processing flow, it retrieves and processes log copies, leaving the main transaction system unchanged and maintaining high productivity while achieving precise measurement.
3Measurement precision
If detailed reporting is required from application programs, then measurement precision is improved, but ease of operation worsens
Solution Approach 1:
The timestamp service is self-service in that it automatically retrieves execution log data, identifies relevant events, matches them with timestamps, and generates timing information without requiring application programs to perform these complex operations. Application programs simply need to log events with basic identifiers, while the timestamp service handles all the sophisticated matching and timing calculation independently.
Data Source
AI summary
A method of documenting occurrence of an event in a computer system includes receiving first event information forwarded upon a first event occurring in execution of a first step in a transaction process. The first event information includes a first step key, a first step type, and first time-of-occurrence information. The method includes identifying, upon receiving the first event information, an anchor step type that previously has been assigned for use in documenting the first event. The anchor step type is associated with an anchor step in the transaction process. The method includes reading, using the anchor step type, an anchor key of the anchor step in an execution log for the transaction process. The execution log is identified using the first step key. The method includes associating the anchor key with the first time-of-occurrence information. A performance measure having start and end events may be evaluated.