System and method for instrumenting a software application

• US 20050182750A1
• Filed: 02/11/2005
• Published: 08/18/2005
• Est. Priority Date: 02/13/2004
• Status: Abandoned Application

• Current Assignee: Fis Financial Compliance Solutions LLC (Fidelity National Information Services Incorporated)
• Original Assignee: Memento Inc. (Fidelity National Information Services Incorporated)
• Inventors: Bammi, Jwahar R., Krishna, Bagepalli C.
• Application Number:
  US11/056,576
• Publication Number:
  US 20050182750A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3438 monitoring of user actions tracking the activity of the user H04L67/535
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466
• CPC Class Codes: G06F 11/3616 using software metrics
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 21/16 Program or content traceability, e.g. by watermarking
• CPC Class Codes: G06F 21/552 involving long-term monitoring or reporting
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/87 Monitoring of transactions

Abstract

A method of instrumenting a software application includes tracing events associated with a usage scenario of the software application; pruning the traced events to produce a signature profile representative of a subset of the traced events, the subset being correlated with the usage scenario; and inserting tags corresponding to the signature profile into the software application for monitoring an additional usage scenario of the software application. Monitoring the additional usage scenario includes detecting a subset of the inserted tags. A further, optional, step of the method includes comparing the detected tags with the signature profile to determine whether a match exists between the usage scenario and the additional usage scenario. Optionally, the method generates a report containing information about the additional usage scenario, in particular information at the detected tags.

Claims

1. A method of instrumenting at least one software application, comprising:

tracing events associated with a first operation of the at least one software application;

determining a first signature profile representative of a subset of the traced events correlated with the first operation; and

inserting tags corresponding to the first signature profile into the at least one software application for monitoring at least one additional operation of the at least one software application.

2. The method of claim 1, including monitoring a second operation of the at least one software application at least in part by detecting a subset of the inserted tags in the second operation.

3. The method of claim 2, wherein the monitoring includes detecting the subset of the inserted tags according to a detection sequence.

4. The method of claim 2, wherein the monitoring includes detecting the subset of the inserted tags according to a schedule.

5. The method of claim 2, wherein the monitoring includes collecting information about the second operation at one or more detected tags belonging to the detected subset of the inserted tags.

6. The method of claim 5, wherein the collected information includes event data associated with the second operation.

7. The method of claim 5, including storing the collected information for subsequent processing.

8. The method of claim 2 including matching with the first signature profile one or more detected tags belonging to the detected subset of the inserted tags.

9. The method of claim 8, including declaring a match between the first and second operations of the at least one software application if a match is determined between the one or more detected tags and the first signature profile.

10. The method of claim 9, wherein declaring the match between the first and second operations includes generating a report associated with the second operation.

11. The method of claim 10, wherein generating the report includes indicating a risk associated with the second operation.

12. The method of claim 10, wherein generating the report includes indicating a performance metric of at least one business process represented at least in part by the at least one software application working in concert.

13. The method of claim 1, wherein inserting the tags includes injecting code blocks into the at least one software application, the injected code blocks corresponding to one or more software application instructions executed as part of the first operation of the at least one software application.

14. The method of claim 13, wherein injecting the code blocks includes coupling to a software interface of the at least one software application.

15. The method of claim 14, wherein the software interface includes a runtime environment interface of at least one software language used to produce the at least one software application.

16. The method of claim 14, wherein coupling to the software interface includes detecting at least one software runtime event.

17. The method of claim 16, wherein a subset of the at least one software runtime event corresponds to one or more of:

a method call, a method return, a line number of executing software, an object creation, a memory allocation, a COM interface call, a COM interface return, a Java Bean event, a J2EE Bean event, a library load, a library unload, a file system event, a TCP/IP stack level transmit event, a TCP/IP stack level receipt event, an SQL event, a transactional bus event, an MQ series event, an MSMQ series event, a web service event, and a notification framework event.

18. The method of claim 1, wherein at least one of the first and the at least one additional operations includes a plurality of temporally-distributed executions of at least one of the at least one software application.

19. The method of claim 1, including,

tracing additional events associated with the at least one additional operation;

determining at least one additional signature profile representative of a subset of the traced additional events, the at least one additional signature profile respectively correlated with the at least one additional operation; and

inserting additional tags corresponding to the at least one additional signature profile into the at least one software application, thereby creating a library of signature profiles including the first and the at least one additional signature profiles.

20. The method of claim 19, including selecting one of the first and the at least one additional operation as a reference operation having an associated reference signature profile.

21. The method of claim 20, including monitoring a subsequent operation of the at least one software application at least in part by detecting a subset of the inserted tags and a subset of the inserted additional tags in the subsequent operation.

22. The method of claim 21, wherein the subsequent monitoring includes detecting the subset of the inserted tags and the subset of the inserted additional tags in sequence.

23. The method of claim 21, wherein the subsequent monitoring includes detecting the subset of the inserted tags and the subset of the inserted additional tags according to a specified schedule.

24. The method of claim 21, wherein the subsequent monitoring includes collecting information about the subsequent operation at one or more detected tags belonging to one or more of the detected subset of the inserted tags and the detected subset of the inserted additional tags.

25. The method of claim 24, wherein the information collected about the subsequent operation includes event data associated with the subsequent operation.

26. The method of claim 24, including storing the information collected about the subsequent operation for further processing.

27. The method of claim 21, including matching with the reference signature profile the tags detected in the subsequent operation.

28. The method of claim 27, including declaring an occurrence of reference operation if a match is determined between the tags detected in the subsequent operation and the reference signature profile.

29. The method of claim 27, including determining a difference between the tags detected in the subsequent operation and the reference signature profile.

30. The method of claim 29, including assigning a risk associated with the subsequent operation at least in part based on the determined difference.

31. The method of claim 29, including assigning a performance metric to at least one business process represented at least in part by the subsequent operation of the at least one software application working in concert.

32. A method of developing a signature profile associated with an operation of a software application, comprising:

executing the software application according to the operation;

tracing events that occur as part of executing the software application according to the operation; and

determining a signature profile by selecting a subset of the traced events correlated with, and representative of, the operation.

33. A software tool for instrumenting at least one software application, the software tool stored in a computer-readable medium, executing at least in part on an application server, and comprising:

a tracer that traces events associated with a first operation of the at least one software application;

a signature profiler that produces a first signature profile by selecting a subset of the traced events correlated with the first operation; and

a code injector that inserts tags corresponding to the first signature profile into the at least one software application for monitoring at least one additional operation of the at least one software application.

34. The software tool of claim 33, including a detector that detects a subset of the inserted tags in a second operation of the at least one software application.

35. The software tool of claim 33, including a matcher that matches the detected tags with the first signature profile.

36. The software tool of claim 33, including a graphical user interface that provides a menu of options to enable a user to control a behavior of the software tool.

37. The software tool of claim 33, including a repository that stores at least one of signature profile data, event data, and match data associated with at least one of the first and the at least one additional operations.

38. The software tool of claim 33, including a scheduler that schedules a time frame for monitoring the at least one additional operation.