Method and apparatus for analysis of runtime behavior
A method comprising: receiving a configuration file that identifies a plurality of first log patterns, each of the first log patterns being associated with a respective component of an application and a respective malfunction of the respective component of the application; retrieving, by an application monitor, one more execution logs that are generated while the application is being executed; identifying, by the application monitor, a malfunction of the application based on the configuration file and the one or more execution logs, the malfunction being identified in response to a given one of the plurality of first log patterns matching an execution log pattern that is identified in the one or more execution logs; and reporting, by the application monitor, the malfunction to a technical support system.
1. A method, comprising:
receiving a configuration file that identifies a plurality of first log patterns, the configuration file being arranged to identify a respective component of an application that is associated with each of the plurality of first log patterns, at least one of the first log patterns identifying a sequence of actions that are taken by the application and an outcome of the sequence of actions;
retrieving, by an application monitor, one or more execution logs that are generated while the application is being executed;
identifying, by the application monitor, a malfunction of the application based on the configuration file and the one or more execution logs, the malfunction being identified in response to a given one of the plurality of first log patterns matching an execution log pattern that is identified in the one or more execution logs; and
reporting, by the application monitor, the malfunction to a technical support system,
wherein reporting the malfunction to the technical support system includes retrieving, from the configuration file, an identifier of a component of the application that is associated with the given one of the plurality of first log patterns and transmitting the retrieved identifier to the technical support system, and
wherein the application monitor is executed concurrently with the application on a same computing device, and the malfunction of the application is identified and reported while the application is being executed.
2. The method of claim 1 , wherein the configuration file further identifies a plurality of second log patterns, each of the second log patterns being associated with a respective component of an application and a respective normal operational state of the respective component of the application.
3. The method of claim 1 , wherein reporting the malfunction includes transmitting to the technical support system an identifier of the respective component of the application that is associated with the given one of the plurality of first log patterns.
4. The method of claim 1 , wherein the application monitor is configured to iteratively compare the one or more execution logs of the application to the configuration file, as the one or more execution logs of the application are being updated over the course of execution of the application.
5. The method claim 1 , wherein the plurality of first logs is generated by processing one or more test logs that are generated during a testing of the application.
6. The method of claim 1 , the configuration file is received concurrently with an executable file for the application.
7. The method of claim 6 , wherein the executable file for the application and the configuration file are packaged together.
8. A system, comprising:
a memory; and
at least one processor operatively coupled to the memory, the at least one processor being configured to perform the operations of:
receiving a configuration file that identifies a plurality of first log patterns, the configuration file being arranged to identify a respective component of an application that is associated with each of the plurality of first log patterns, at least one of the first log patterns identifying a sequence of actions that are taken by the application and an outcome of the sequence of actions;
retrieving, by an application monitor, one or more execution logs that are generated while the application is being executed;
identifying, by the application monitor, a malfunction of the application based on the configuration file and the one or more execution logs, the malfunction being identified in response to a given one of the plurality of first log patterns matching an execution log pattern that is identified in the one or more execution logs; and
reporting, by the application monitor, the malfunction to a technical support system,
wherein reporting the malfunction to the technical support system includes retrieving, from the configuration file, an identifier of a component of the application that is associated with the given one of the plurality of first log patterns and transmitting the retrieved identifier to the technical support system, and
wherein the application monitor is executed concurrently with the application on a same computing device, and the malfunction of the application is identified and reported while the application is being executed.
9. The system of claim 8 , wherein the configuration file further identifies a plurality of second log patterns, each of the second log patterns being associated with a respective component of an application and a respective normal operational state of the respective component of the application.
10. The system of claim 8 , wherein reporting the malfunction includes transmitting to the technical support system an identifier of the respective component of the application that is associated with the given one of the plurality of first log patterns.
11. The system of claim 8 , wherein the application monitor is configured to iteratively compare the one or more execution logs of the application to the configuration file, as the one or more execution logs of the application are being updated over the course of execution of the application.
12. The system of claim 8 , wherein the plurality of first logs is generated by processing one or more test logs that are generated during a testing of the application.
13. The system of claim 8 , the configuration file is received concurrently with an executable file for the application.
14. The system of claim 13 , wherein the executable file for the application and the configuration file are packaged together.
15. A non-transitory computer-readable storage medium that is configured to store one or more processor-executable instructions, which when executed by at least one processor cause the at least one processor to perform the operations of:
receiving a configuration file that identifies a plurality of first log patterns, the configuration file being arranged to identify a respective component of an application that is associated with each of the plurality of first log patterns, at least one of the first log patterns identifying a sequence of actions that are taken by the application and an outcome of the sequence of actions;
retrieving, by an application monitor, one or more execution logs that are generated while the application is being executed;
identifying, by the application monitor, a malfunction of the application based on the configuration file and the one or more execution logs, the malfunction being identified in response to a given one of the plurality of first log patterns matching an execution log pattern that is identified in the one or more execution logs; and
reporting, by the application monitor, the malfunction to a technical support system,
wherein reporting the malfunction to the technical support system includes retrieving, from the configuration file, an identifier of a component of the application that is associated with the given one of the plurality of first log patterns and transmitting the retrieved identifier to the technical support system, and
wherein the application monitor is executed concurrently with the application on a same computing device, and the malfunction of the application is identified and reported while the application is being executed.
16. The non-transitory computer-readable storage medium of claim 15 , wherein the configuration file further identifies a plurality of second log patterns, each of the second log patterns being associated with a respective component of an application and a respective normal operational state of the respective component of the application.
17. The non-transitory computer-readable storage medium of claim 15 , wherein reporting the malfunction includes transmitting to the technical support system an identifier of the respective component of the application that is associated with the given one of the plurality of first log patterns.
18. The non-transitory computer-readable storage medium of claim 15 , wherein the application monitor is configured to iteratively compare the one or more execution logs of the application to the configuration file, as the one or more execution logs of the application are being updated over the course of execution of the application.
19. The non-transitory computer-readable storage medium of claim 15 , wherein the plurality of first logs is generated by processing one or more test logs that are generated during a testing of the application.
20. The non-transitory computer-readable storage medium of claim 15 , the configuration file is received concurrently with an executable file for the application.