Linking Single System Synchronous Inter-Domain Transaction Activity

Abstract

An approach is provided to correlate transaction data occurring at two different domains running on a common operating system image without using static, or common, correlators. Request-type event records are collected at a first domain within the operating system image, with each of the request-type event records including execution identifiers and a unique token that indicates the order in which the corresponding request-type event occurred on the first domain. Similarly, response-type event records are collected at a second domain within the operating system image. The request-type event records are matched with the response-type event records based on the execution identifiers and an overall order that is indicated by unique tokens included in the records. The matching of request-type event records with response-type event records indicate a number of inter-domain transactions which are recorded in a correlation data store.

1 . (canceled) 
     
     
         2 . (canceled) 
     
     
         3 . (canceled) 
     
     
         4 . (canceled) 
     
     
         5 . (canceled) 
     
     
         6 . (canceled) 
     
     
         7 . (canceled) 
     
     
         8 . An information handling system comprising:
 one or more processors;   a memory coupled to at least one of the processors;   an operating system image stored in the memory and executed by at least one of the processors;   a first domain within the operating system image from which a plurality of request-type event records are collected and stored in a first data store, wherein each of the request-type event records includes one or more execution identifiers and a first unique token that indicates a first order in which the corresponding request-type event occurred;   a second domain within the operating system image from which a plurality of response-type event records are collected and stored in a second data store, wherein each of the response-type event records also includes one or more of the execution identifiers and a second unique token that indicates a second order in which the corresponding response-type event occurred; and   a set of instructions stored in the memory and executed by at least one of the processors, wherein the set of instructions perform actions of:
 receiving the plurality of request-type event records and the plurality of response-type event records; 
 matching each of the plurality of request-type event records with one of the plurality of response-type event records based on the execution identifiers and an overall processing order indicated by the first and second unique tokens, wherein the matching request-type event records and response-type event records indicate a plurality of inter-domain transactions; and 
 recording the plurality of inter-domain transactions in a correlation data store. 
   
     
     
         9 . The information handling system of  claim 8  wherein the set of instructions performs additional actions comprising:
 merging the plurality of request-type event records with the plurality of response-type event records based on the respective first and second unique tokens. 
 
     
     
         10 . The information handling system of  claim 8  wherein the matching further comprises:
 ensuring a lack of intervening request-type events with the same execution identifiers between the request-type event records and the response-type event records. 
 
     
     
         11 . The information handling system of  claim 8  wherein the execution identifiers include a system identifier, a process identifier, and a thread identifier. 
     
     
         12 . The information handling system of  claim 8  wherein the set of instructions performs additional actions comprising:
 analyzing the recorded plurality of inter-domain transactions, wherein the analyzing results in an analysis of inter-domain transactions. 
 
     
     
         13 . The information handling system of  claim 8  wherein the set of instructions performs additional actions comprising:
 identifying at least one of the request-type event records that does not match to one of the response-type event records; and 
 recording the identified request-type event records to an error log. 
 
     
     
         14 . The information handling system of  claim 8  wherein the first and second unique tokens are based on a timestamp. 
     
     
         15 . A computer program product stored in a computer readable medium, comprising functional descriptive material that, when executed by an information handling system, causes the information handling system to perform actions that include:
 receiving a plurality of request-type event records collected at a first domain within an operating system image, wherein each of the request-type event records includes one or more execution identifiers and a first unique token that indicates a first order in which the corresponding request-type event occurred;   receiving a plurality of response-type event records collected at a second domain within the operating system image, wherein each of the response-type event records also includes one or more of the execution identifiers and a second unique token that indicates a second order in which the corresponding response-type event occurred;   matching each of the plurality of request-type event records with one of the plurality of response-type event records based on the execution identifiers and an overall order indicated by the first and second unique tokens, wherein the matching request-type event records and response-type event records indicate a plurality of inter-domain transactions; and   recording the plurality of inter-domain transactions in a correlation data store.   
     
     
         16 . The computer program product of  claim 15  wherein the actions further comprise:
 merging the plurality of request-type event records with the plurality of response-type event records based on the respective first and second unique tokens. 
 
     
     
         17 . The computer program product of  claim 15  wherein the matching further comprises:
 ensuring a lack of intervening request-type events with the same execution identifiers between the request-type event records and the response-type event records. 
 
     
     
         18 . The computer program product of  claim 15  wherein the execution identifiers include a system identifier, a process identifier, and a thread identifier. 
     
     
         19 . The computer program product of  claim 15  wherein the actions further comprise:
 analyzing the recorded plurality of inter-domain transactions, wherein the analyzing results in an analysis of inter-domain transactions. 
 
     
     
         20 . The computer program product of  claim 15  wherein the actions further comprise:
 identifying at least one of the request-type event records that does not match to one of the response-type event records; and 
 recording the identified request-type event records to an error log. 
 
     
     
         21 . The computer program product of  claim 15  wherein the first and second unique tokens are based on a timestamp. 
     
     
         22 . (canceled) 
     
     
         23 . (canceled) 
     
     
         24 . (canceled) 
     
     
         25 . (canceled)