METHOD AND SYSTEM FOR CORRELATING TRACE DATA

• US 20090204947A1
• Filed: 02/12/2008
• Published: 08/13/2009
• Est. Priority Date: 02/12/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation, ServiceNow Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Derdak, Stefan Georg, Claussen, Christopher Shane, Mei, Xiaochun, Barker, Kevin Spencer
• Granted Patent: US 8,601,443 B2
• Time in Patent Office: Days
• US Class Current: 717/125
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program

Abstract

A computer program product comprises a computer useable medium. The computer useable medium has a computer readable program such that when the computer readable medium is executed on a computer, the computer is caused to configure a calling interceptor at a service invocation point corresponding to a first component service of a software application to monitor a service invocation made by the first component service of a second component service of the software application, record a first set of correlation data represented by a first correlation indicator into a trace file, record a unique identifier into the trace file, and send the unique identifier to the second component service thought the service invocation.

Claims

1. A computer program product comprising a computer useable medium having a computer readable program, wherein the computer readable program when executed on a computer causes the computer to:

configure a calling interceptor at a service invocation point corresponding to a first component service of a software application to monitor a service invocation made by the first component service of a second component service of the software application, record a first set of correlation data represented by a first correlation indicator into a trace file, record a unique identifier into the trace file, and send the unique identifier to the second component service through the service invocation;

configure a callee interceptor at a service invocation point corresponding to a second component service of the software application to monitor the service invocation made by the first component service of the second component service of the software application, record a second set of correlation data represented by a second correlation indicator into the trace file, obtain the unique identifier from the service invocation, and record the unique identifier into the trace file; and

correlate trace data from the first component service and the second component service based on the first correlation indicator, the second correlation indicator, and the unique identifier.

2. The computer program product of claim 1, wherein the service invocation is asynchronous.

3. The computer program product of claim 1, wherein the first component service is stored in a first component and the second component service is stored in a second component, the first component distinct from the second component.

4. The computer program product of claim 1, wherein the first component service is stored in a first server and the second component service is stored in a second server, the first server distinct from the second server.

5. The computer program product of claim 1, wherein the computer readable program when executed on the computer further causes the computer to process the service invocation at the first component service utilizing a first thread and process the service invocation at the second component service utilizing a second thread, the first thread distinct from the second thread.

6. The computer program product of claim 1, wherein the computer readable program when executed on the computer further causes the computer to display the trace data that is correlated.

7. The computer program product of claim 1, wherein the computer readable program when executed on the computer further causes the computer to randomly generate the unique identifier.

8. The computer program product of claim 1, wherein the computer readable program when executed on the computer further causes the computer to process a plurality of events and record a unique event identifier for each event in the trace file.

9. The computer program product of claim 8, wherein the computer readable program when executed on the computer further causes the computer to additionally correlate the trace data based on the unique event identifier.

10. The computer program product of claim 8, wherein the computer readable program when executed on the computer further causes the computer to randomly generate the unique identifier.

11. The computer program product of claim 1, wherein the software application is built on top of a Service Oriented Architecture.

12. A method comprising:

configuring a calling interceptor at a service invocation point corresponding to a first component service of a software application to monitor a service invocation made by the first component service of a second component service of the software application, record a first set of correlation data represented by a first correlation indicator into a trace file, record a unique identifier into the trace file, and send the unique identifier to the second component service through the service invocation;

configuring a callee interceptor at a service invocation point corresponding to a second component service of the software application to monitor the service invocation made by the first component service of the second component service of the software application, record a second set of correlation data represented by a second correlation indicator into the trace file, obtain the unique identifier from the service invocation, and record the unique identifier into the trace file; and

correlating trace data from the first component service and the second component service based on the first correlation indicator, the second correlation indicator, and the unique identifier.

13. The method of claim 12, wherein the service invocation is asynchronous.

14. The method of claim 12, wherein the first component service is stored in a first component and the second component service is stored in a second component, the first component distinct from the second component.

15. The method of claim 12, wherein the first component service is stored in a first server and the second component service is stored in a second server, the first server distinct from the second server.

16. The method of claim 12, further comprising processing the service invocation at the first component service utilizing a first thread and process the service invocation at the second component service utilizing a second thread, the first thread distinct from the second thread.

17. The method of claim 12, further comprising displaying the trace data that is correlated.

18. A system comprising:

a calling interceptor positioned at a service invocation point corresponding to a first component service of a software application that monitors a service invocation made by the first component service of a second component service of the software application, records a first set of correlation data represented by a first correlation indicator into a trace file, records a unique identifier into the trace file, and sends the unique identifier to the second component service through the service invocation;

a callee interceptor positioned at a service invocation point corresponding to a second component service of the software application that monitors the service invocation made by the first component service of the second component service of the software application, records a second set of correlation data represented by a second correlation indicator into the trace file, obtains the unique identifier from the service invocation, and records the unique identifier into the trace file; and

a correlation module that correlates trance data from the first component service and the second component service based on the first correlation indicator, the second correlation indicator, and the unique identifier.

19. The system of claim 18, wherein the service invocation is asynchronous.

20. The system of claim 18, further comprising a display module that displays the trace data that is correlated.