One of the best features added to the K2.NET product with the release of “Service Pack 4” was the K2.net 2003 Logging and Performance Monitoring Frameworks.
This allows a developer or IT.Admin to persist the K2.NET server log, with ALL actions – just like “SQL Server Profiler” does.
The K2.net 2003 Logging and Performance Monitoring Frameworks facilitate the logging of all Informational, Debug and Error messages and the reporting of Performance Metrics related to K2.net 2003 Server.
Will delve into the “PerfMon” aspects later – also very cool.
One of the drawbacks to the Logging Framework is that the messages are simply dumped into a text, and they’re about as readible as an IIS log…>
#Software: Microsoft Internet Information Services 5.1
#Date: 2007-02-24 23:24:35
#Fields: time c-ip cs-method cs-uri-stem sc-status
23:24:35 10.10.10.101 GET /VirtualServer/VSWebApp.exe 401
23:24:35 10.10.10.101 GET /VirtualServer/VSWebApp.exe 200
23:24:35 10.10.10.101 GET /VirtualServer/scripts/VSScripts.js 401
23:24:35 10.10.10.101 GET /VirtualServer/scripts/VSScripts.js 200
23:24:35 10.10.10.101 GET /VirtualServer/scripts/VSStyles.css 200
23:24:35 10.10.10.101 GET /VirtualServer/images/pagehead-right.gif 200
Sergio Del Piccolo has created a very useful WinApp that opens the Log File in a grid – with a number of filter fields to delve into the log file output.
From this :
To this :
Full story here.
Further article about the Logging Framework here.