I've just updated the EDocsLogParser tool. Now it can process Hummingbird DM 5.2.1 server logs in addition to OpenText eDOCS DM 5.3.1 supported from the initial version. Additionally, a few issues were fixed, and I've made some minor cosmetic tweaks.
Binaries: EDocsLogParser v1.0.4 x64/x86 for Windows
Source: https://github.com/dotnetnick/edocs/
User Guide: EDocsLogParser Usage
And let's not forget why we parse DM Server logs:
How to Find Slow SQL Queries in eDOCS DM Server Logs
How to Determine the Right Size for SQL Connection Cache
These are just examples. You can also think out other applications for the data from the logs.
If you process huge logs (greater than 1.5 GB), you should use x64 version of EDocsLogParser.exe. For smaller log files it doesn't matter: both 32- and 64-bit versions should work equally well. The tool consumes around the same amount of memory as the size of the log file. If you have 4 GB of RAM on your system, it should be fine for processing logs up to 2 GB, though the more memory your system has, the better.
Any feedback is welcome. Thank you!
Binaries: EDocsLogParser v1.0.4 x64/x86 for Windows
Source: https://github.com/dotnetnick/edocs/
User Guide: EDocsLogParser Usage
And let's not forget why we parse DM Server logs:
How to Find Slow SQL Queries in eDOCS DM Server Logs
How to Determine the Right Size for SQL Connection Cache
These are just examples. You can also think out other applications for the data from the logs.
If you process huge logs (greater than 1.5 GB), you should use x64 version of EDocsLogParser.exe. For smaller log files it doesn't matter: both 32- and 64-bit versions should work equally well. The tool consumes around the same amount of memory as the size of the log file. If you have 4 GB of RAM on your system, it should be fine for processing logs up to 2 GB, though the more memory your system has, the better.
Any feedback is welcome. Thank you!
No comments:
Post a Comment