This is the second post about parsing Hummingbird DM / OpenText eDOCS DM server logs. Part #1 is here.
In this part I'm going to briefly explain the structure of the log parser just in case anyone may want to recompile, modify or extend it. However, if you simply want to get the DM Log Parser executable and use it, please feel free to jump directly to Part #3 - Usage of this article series.
The EDocsLogParser solution is implemented in C# / Visual Studio 2013 and consists of 3 projects.
Currently, the log parser can extract SQL events from a DM Server log file. It works for any log file, but, apparently, events will be extracted only if the log file was created with Log SQL, Log SQL & Calls, or Log All logging level:
Full source code of EDocsLogParser: https://github.com/dotnetnick/edocs/
In this part I'm going to briefly explain the structure of the log parser just in case anyone may want to recompile, modify or extend it. However, if you simply want to get the DM Log Parser executable and use it, please feel free to jump directly to Part #3 - Usage of this article series.
The EDocsLogParser solution is implemented in C# / Visual Studio 2013 and consists of 3 projects.
Currently, the log parser can extract SQL events from a DM Server log file. It works for any log file, but, apparently, events will be extracted only if the log file was created with Log SQL, Log SQL & Calls, or Log All logging level:
Full source code of EDocsLogParser: https://github.com/dotnetnick/edocs/
No comments:
Post a Comment