A new look at diagnostic reporting
Ravi G 120000NSV8 Visits (3400)
Many monitoring and diagnostic tools provide reporting. There are various types of reports generated for different sets of consumers: Managers, Operators, Subject matter experts (SME) etc. The reports that are currently generated are mostly static in nature available in PDF, HTML and other formats.
Many times the static diagnostic reports generated for SMEs are not sufficient in terms of data. The SME looks at the report and often times works with the production administrator to either schedule or configure new reports. This process often requires going back and forth multiple times. In many companies this cycle can be expensive in terms of time as it involves raising a request and getting required approvals.
To reduce the turnaround time, a more useful approach is a dynamic report that captures lot of details that the SME can filter and analyze. The report can remain lightweight by using formats like JSON. The meta data required to interpret and render the report can be made available separately as an Eclipse plug-in to facilitate integration with SME or developer environments.
An Eclipse tool can import the data and help guide the user towards a problem by presenting detailed data at class and method level with sequence diagrams, tree views etc that the SME is familiar with. The SME can do a deep dive to analyze various other segments and hotspots, filter and group data differently. Sometimes root cause analysis requires examining multiple hot spots and developing a problem pattern.
IBM Application Performance Diagnostics Lite introduces this kind of reporting and we will talk more about it in future blogs.
Please see IBM Application Performance Diagnostics beta site herehttp