AUTOMATICALLY CORRELATING TRANSACTION EVENTS

• US 20100313202A1
• Filed: 06/04/2009
• Published: 12/09/2010
• Est. Priority Date: 06/04/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Wilkins, Andrew
• Granted Patent: US 8,479,220 B2
• Time in Patent Office: Days
• US Class Current: 718/100
• CPC Class Codes: G06F 9/466 Transaction processing

Abstract

An API can be extended to automatically correlate events based on context. Started events for each context (e.g. threads of execution) are maintained on independent stacks. When an instrumented application starts a new transaction, the API generates a started event. A transaction correlation unit within the API can determine if the new transaction started during a previous transaction. If there is a previous started event on the stack, the new transaction started during the previous transaction. The transaction correlation unit can insert an outbound indicator into the new started event to associate the new transaction and the previous transaction. Then, the new started event can be pushed on the stack.

Claims

1. A computer implemented method comprising:

detecting that a first transaction has started;

generating a first started event for the first transaction;

determining if the first transaction started during a second transaction;

inserting an outbound indicator identifying the second transaction into the first started event to indicate that the first transaction is a sub-transaction of the second transaction if it is determined that the first transaction started during the second transaction; and

storing the first started event in a data structure.

2. The computer implemented method of claim 1, wherein said detecting that the first transaction has started further comprises detecting an application programming interface call.

3. The computer implemented method of claim 1, wherein the data structure comprises a stack.

4. The computer implemented method of claim 1 further comprising determining that a second started event is stored in the data structure.

5. The computer implemented method of claim 1, wherein said inserting the outbound indicator identifying the second transaction into the first started event to indicate that the first transaction is a sub-transaction of the second transaction comprises:

determining an identifier of the second transaction based on a second started event stored in the data structure; and

storing the identifier in a data member of the first started event, wherein the first started event comprises a set of data members that represent data related to the first transaction.

6. The computer implemented method of claim 1, wherein said inserting the outbound indicator identifying the second transaction into the first started event to indicate that the first transaction is a sub-transaction of the second transaction comprises inserting, into the first started event, a first inbound indicator identifying the first transaction.

7. The computer implemented method of claim 1 further comprises:

detecting that the first transaction is ending;

generating a finished event for the first transaction;

determining if the first transaction started during the second transaction based, at least in part, on the outbound indicator of the first start event;

inserting an inbound indicator identifying the second transaction into the finished event to indicate that the first transaction is a sub-transaction of the second transaction if the first transaction started during the second transaction; and

removing the first started event from the data structure.

8. The computer implemented method of claim 7 further comprising determining that an outbound indicator identifies the second transaction.

9. A computer program product for automatically correlating transaction events, the computer program product comprising:

a computer usable medium having computer usable program code embodied therewith, the computer usable program code comprising;

computer usable program code configured to,

detect that a first transaction has started;

generate a first started event for the first transaction;

determine if the first transaction started during a second transaction;

insert an outbound indicator identifying the second transaction into the first started event to indicate that the first transaction is a sub-transaction of the second transaction if the first transaction started during the second transaction; and

store the first started event in a data structure of started events.

10. The computer program product of claim 9, wherein the computer usable program code is further configured to determine that a second started event is stored in the data structure.

11. The computer program product of claim 9, wherein said computer usable program code being configured to insert the outbound indicator identifying the second transaction into the first started event to indicate that the first transaction is a sub-transaction of the second transaction comprises the computer usable code being configured to:

determine an identifier of the second transaction based on a second started event stored in the data structure; and

store the identifier in a data member of the first started event, wherein the first started event comprises a set of data members that store data related to the first transaction.

12. The computer program product of claim 9, wherein the computer usable code is further configured to:

detect that the first transaction is ending;

generate a finished event for the first transaction;

determine if the first transaction started during the second transaction based, at least in part, on the outbound indicator of the first start event;

insert an inbound indicator identifying the second transaction into the finished event to indicate that the first transaction is a sub-transaction of the second transaction if the first transaction started during the second transaction; and

remove the first started event from the data structure.

13. The computer program product of claim 12, wherein the computer usable code being further configured to determine that an outbound indicator identifies the second transaction.

14. A computer program product for automatically correlating transaction events, the computer program product comprising:

a computer usable medium having computer usable program code embodied therewith, the computer usable program code comprising;

computer usable program code configured to,

detect that a first transaction is ending;

generate a finished event for the first transaction;

determine if the first transaction started during a second transaction based, at least in part, on an outbound indicator of a started event for the first transaction, wherein the outbound indicator indicates the second transaction;

insert an inbound indicator identifying the second transaction into the finished event to indicate that the first transaction is a sub-transaction of the second transaction if the first transaction started during the second transaction; and

remove the started event from a data structure of started events.

15. The computer program product of claim 14, wherein the computer usable code being further configured to determine that an outbound indicator identifies the second transaction.

16. An apparatus comprising:

a processing unit;

a network interface; and

a transaction correlation unit operable to,

detect that a first transaction has started;

generate a first started event for the first transaction;

determine if the first transaction started during a second transaction;

insert an outbound indicator identifying the second transaction into the first started event to indicate that the first transaction is a sub-transaction of the second transaction if the first transaction started during the second transaction; and

store the first started event in a data structure.

17. The apparatus of claim 16, wherein the transaction correlation unit being further operable to determine that a second started event is stored in the data structure.

18. The apparatus of claim 16, wherein said the transaction correlation unit being operable to insert the outbound indicator identifying the second transaction into the first started event to indicate that the first transaction is a sub-transaction of the second transaction further comprises the transaction correlation unit being operable to:

determine an identifier of the second transaction based on a second started event stored in the data structure; and

store the identifier in a data member of the first started event, wherein the first started event comprises a set of data members that store data related to the first transaction.

19. The apparatus of claim 16 further comprises the transaction correlation unit being operable to:

detect that the first transaction is ending;

generate a finished event for the first transaction;

determine if the first transaction started during a second transaction based, at least in part, on the outbound indicator of the first start event;

insert an inbound indicator identifying a second transaction into the finished event to indicate that the first transaction is a sub-transaction of the second transaction if the first transaction started during the second transaction; and

remove the first started event from the data structure.

20. The apparatus of claim 19, wherein the transaction correlation unit being further operable to determine that an outbound indicator identifies the second transaction.