Browse Prior Art Database

Method for automating diagnostic data collection for software applications

IP.com Disclosure Number: IPCOM000240854D
Publication Date: 2015-Mar-06
Document File: 2 page(s) / 126K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article outlines an automated solution for collecting diagnostic data for any software application. The automated diagnostic data collection is accomplished by monitoring an application's log file(s) for one or more occurances of a specific message or message pattern. Once the message of interest appears in the application's log file, the automation dumps the application's address space and saves the diagnostic data so that it may be further analyzed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 2

Method for automating diagnostic data collection for software applications

There exists automated solutions for collecting diagnostic data for specific software applications ; however, most of these solutions require internal hooks to be implemented in the software application itself that allow for key diagnostic data to be dumped and collected for analysis. For example IBM's mainframe operating system z/OS has a SLIP feature that can be used to dynamically collect diagnostic data triggered by a certain message ID appearance in the system log , or an application abend. The drawback to using the SLIP is that it requires internal hooks that must be implemented in the application being monitored, or it must write WTO messages to the system log. Another existing solution is Microsoft's Diagnostic Data Adapter; however, this solution must be used in the implementation of the third-party application. Another pervasive solution is strictly application-specific, e.g. IBM Notes has a feature that automatically collects diagnostic data that can be sent to developers if the application crashes unexpectedly . Currently, there exists no automated solution for collecting diagnostic data for any third-party software application that does not write WTO messages with distinct message IDs , or explicitly abend.

Prior Art Search Hits:

IBM z/OS SLIP feature: http://pic.dhe.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.ieag100/slip.htm Diagnostic Data Adapter: http://msdn.microsoft.com/en-us/library/dd286727.aspx
IBM Notes Automated Diagnostic Data Collection: http://www-01.ibm.com/support/docview.wss?uid=swg21085850

The differentiating factor of this proposed solution is that the solution will allow users to specify the third -party application job log(s) that needs to be monitored, and provides the ability to dynamically dump and collect diagnostic data based on one or more occurrences of a specific message or message pattern in the application 's job log. For example, if a user wishes to collect diagnostic data based on an application's storage usage, and there exists a display in the log which contains a fill-in value that lists current storage usage, this solution...