P
USRE49366EActiveUtilityPatentIndex 56

Correlation across non-logging components

Assignee: MICROSOFT TECHNOLOGY LICENSING LLCPriority: Aug 11, 2017Filed: Nov 16, 2021Granted: Jan 10, 2023
Est. expiryAug 11, 2037(~11.1 yrs left)· nominal 20-yr term from priority
Inventors:WRIGHT DAVID CHRISTOPHERCHATTERJEE ARIJITYUAN QINGQINGBARLI PRAVEEN KUMARHIREMATH BASAVESHWAR SSYED NOSHEEN MJOHNSON AUTUMN LEE
G06F 9/466G06F 9/546G06N 7/01H04L 67/10G06F 11/2205G06F 11/3006G06F 11/3476G06F 11/14G06F 2201/87G06F 11/3404H04L 67/535G06N 7/005
56
PatentIndex Score
0
Cited by
43
References
18
Claims

Abstract

Systems are provided for logging transactions in heterogeneous networks that include a combination of one or more instrumented components and one or more non-instrumented components. The instrumented components are configured to generate impersonated log records for the non-instrumented components involved in the transaction processing hand-offs with the instrumented components. The impersonated log records are persisted with other log records that are generated by the instrumented components in a transaction log that is maintained by a central logging system to reflect a complete flow of the transaction processing performed on the object, including the flow through the non-instrumented component(s).

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
       1. A computing system comprising a first component that is an instrumented component configured for generating log records for transaction processing associated with a transaction that is processed by multiple components, including at least one component that is not instrumented for logging, the computing system comprising:
 one or more processors; and 
 one or more storage device devices having stored computer-executable instructions that are executable by the one or more processors for causing the first component to perform a method comprising: 
 receiving, at the first component, a transaction to process; 
 creating, at the first component, an initial first component log record; 
 sending the first component log record from the first component to a logging control system; 
 passing, from the first component, the transaction processing off to a next component; 
 determining, by the first component, that the next component is not instrumented for logging, and 
 upon determining that the next component is not instrumented for logging, creating, at the first component, a new component log record associated with processing of the transaction by the next component, and sending the new component log record associated with processing of the transaction by the next component to the logging control system; and 
 the first component creating an additional log record for each different component that the first component passes the transaction processing of to, wherein each additional log record is a unique log record having a unique incremented component value. 
 
     
     
       2. The computing system of  claim 1 , wherein the method further includes creating a secondary first component log record associated with passing the transaction processing off to the next component. 
     
     
       3. The computing system of  claim 2 , wherein the secondary first component log record is a unique log record having a unique incremented component value that distinguishes the secondary first component log record from at least one other secondary first component log record associated with passing the transaction processing off to a different next component. 
     
     
       4. The computing system of  claim 3 , wherein the new component log record includes the a transaction ID, the an incremented component value and a new extension component value that corresponds to processing of the transaction with the new next component. 
     
     
       5. The computing system of  claim 1 , wherein the determining that the next component is not instrumented for logging includes receiving a notification from a remote system other than the next component that the next component is a non-logging component. 
     
     
       6. A computing system comprising a first component that is an instrumented component configured for generating log records for transaction processing associated with a transaction processed by multiple components, including at least one component that is not instrumented for logging, the computing system comprising:
 one or more processors; and 
 one or more storage device devices having stored computer-executable instructions that are executable by the one or more processors for causing the first component to perform a method comprising: 
 receiving, at the first component, a transaction to process; 
 creating, at the first component, a first log record associated with processing the transaction, the first log record including a transaction ID and an initial component value that corresponds to processing of the transaction with the first component; 
 sending the first log record from the first component to a logging control system;
 identifying, at the first component, a next component to pass off the transaction processing to; 
 determining, by the first component, whether the next component is a logging component that is instrumented for logging the transaction processes or, alternatively, a non-logging component that is not instrumented for logging the transaction processes; 
 passing, from the first component, the transaction processing off to the next component; 
 
 creating, at the first component, a second log record, the second log record including the transaction ID and an incremented component value associated with passing the transaction processing off to the next component; and 
 wherein the first component is instrumented to further create, at the first component, a third log record and to send the third log record to the logging control system when it is determined that the next component is not instrumented for logging; and 
 wherein the first component is further configured to create an additional log record for each different component that the first component passes the transaction processing off to, wherein each additional log record is a unique log record having a unique incremented component value. 
 
     
     
       7. The computing system of  claim 6 , wherein the first component is further configured to refrain from creating the third log record upon determining that the next component is instrumented for logging. 
     
     
       8. The computing system of  claim 6 , wherein the third log record includes the transaction ID, the incremented component value and a new extension component value that corresponds to processing of the transaction with the next component. 
     
     
       9. The computing system of  claim 6 , wherein the determining that the next component is not instrumented for logging includes receiving a notification from a remote system other than the next component that the next component is a non-logging component. 
     
     
       10. The method of claim  9  13, wherein the method further includes creating a secondary first component log record associated with passing the transaction processing off to the next component. 
     
     
       11. The computing system method of claim  10  13, wherein the new component log record includes the a transaction ID, the an incremented component value and a new extension component value that corresponds to processing of the transaction with the next component. 
     
     
       12. The computing system method of claim  9  10, wherein the secondary first component log record is a unique log record having a unique incremented component value that distinguishes the secondary first component log record from at least one other secondary first component log record associated with passing the transaction processing off to a different next component. 
     
     
       13. A method implemented by a first component that is instrumented for logging transaction processes associated with a transaction that is processed by multiple components, including at least one component that is not instrumented for logging, the method comprising:
 receiving, at the first component, a transaction to process; 
 creating, at the first component, an initial first component log record; 
 sending the first component log record from the first component to a logging control system; 
 passing, from the first component, the transaction processing off to a next component; 
 determining, by the first component, that the next component is not instrumented for logging, 
 upon determining that the next component is not instrumented for logging, creating, at the first component, a new component log record associated with processing of the transaction by the next component and sending the new component log record associated with the processing of the transaction by the next component to the logging control system; and 
 the first component creating an additional log record for each different component that the first component passes the transaction processing off to, wherein each additional log record is a unique log record having a unique incremented component value. 
 
     
     
       14. A method implemented by a first component that is instrumented for logging transaction processes associated with a transaction that is processed by multiple components, including at least one component that is not instrumented for logging, the method comprising:
 receiving, at the first component, a transaction to process; 
 creating, at the first component, a first log record associated with processing the transaction, the first log record including a transaction ID and an initial component value that corresponds to processing of the transaction with the first component; 
 sending the first log record from the first component to a logging control system; 
 identifying, at the first component, a next component to pass off the transaction processing to; 
 determining, by the first component, whether the next component is a logging component that is instrumented for logging the transaction processes or, alternatively, a non-logging component that is not instrumented for logging the transaction processes; 
 passing, from the first component, the transaction processing off to the next component; 
 creating, at the first component, a second log record, the second log record including the transaction ID and an incremented component value associated with passing the transaction processing off to the next component; 
 wherein the first component is instrumented to further create, at the first component, a third log record and to send the third log record to the logging control system when it is determined that the next component is not instrumented for logging; and 
 wherein the first component is further configured to create an additional log record for each different component that the first component passes the transaction processing off to, wherein each additional log record is a unique log record having a unique incremented component value. 
 
     
     
       15. The method of  claim 14 , wherein the first component is further configured to refrain from creating the third log record upon determining that the next component is instrumented for logging. 
     
     
       16. The method of  claim 14 , wherein the first component is further configured to create an additional log record for each different component that the first component passes the transaction processing off to, wherein each additional log record is a unique log record having a unique incremented component value. 
     
     
       17. The method of  claim 14 , wherein the third log record includes the transaction ID, the incremented component value and a new extension component value that corresponds to processing of the transaction with the next component. 
     
     
       18. The method of  claim 14 , wherein the determining that the next component is not instrumented for logging includes receiving a notification from a remote system other than the next component that the next component is a non-logging component.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.