Essbase application log file parser – The next version

In one of my previous blogs, I had spoken about an Essbase log file parser that I had designed. I did spend some more time redesigning the application so as to make it a bit more user friendly. Also, there were a couple of bugs that I had to iron out in the earlier version uploaded on GitHub. 

The new Essbase Application log file parser when you start it up is as shown in the below snapshot:-

The Essbase log file is the only selectable field where you can either browse the file by clicking on the “Browse” button else you can paste the file name directly. (This was the bug in the earlier version that I have ironed out now)

There are three buttons that can be used for formatting the log file. They are as follows:

Format: This will do a simple text formatting for the log file. This is the basic format which may require more formatting from your end for getting further information.    

Detail: This will do a detailed formatting for the text in the log file. This will separate the timestamp columns, application name, database name, user names and the status code as well along with detailed information.   

Stats: This is similar to the detailed formatting of the text file, but it has a filter associated with it that only retrieves those fields that have a time measure associated with them.

Snapshot of the application and the associated log file parsed is as shown below.

 
The formatted file name is populated only when you click the one of the three buttons that are used for formatting the log file.

The below snapshot shows the file that is generated after clicking the “Format” button.

This is a bare basic version of the log file after parsing and the associated field names is as shown in the below Excel snippet. 

The next snapshot shows the file that is generated after clicking the “Detail” button.

The fields are as shown in the below snapshot.

  

The next snapshot shows the file that is generated after clicking the “Stats” button.

 The fields are tagged as shown in the below snapshot. Most of these fields will have some timing associated with it like restructure time, retrieval time, data export time limit and so on. 

 So basically, it will generate metrics from the Essbase log file. 

I am still testing the application now and I have to add the error handling modules into the application. I am also testing the application and I should be good to upload the application to GitHub within this week.

Will keep you posted!!!