I have just emailed you the files and directions. Please try out the solution and post a response back here with some feedback if you get time. - I'd love to see customers posting here recommending these solutions to other customers and noting down what value they offer.
So nice to see that so many people are interested in getting a copy of Adam's extractor for Prognosis Audit Log.
Just to let everyone who asked for a copy knows, an official version of the extractor will be part of 11.3.
Prior to Prognosis 11.3, Prognosis only had the ability to provide details of various operations performed in a text file or send this audit information out via Syslog. The operations covered include successful and unsuccessful logins from the Prognosis Windows Client and the starting or stopping of Analysts, Thresholds, Databases and Configurations, etc.
In Prognosis 11.3, instead of simply writing this Prognosis audit information to a text file or sending this information to an external Syslog server, a new Prognosis Audit Log record has been created using something very similar to Adam's original extractor.
New packaging has been added to show the information under Windows Client and Web Application including extending the Troubleshooting database on all platforms to store this information. Users will be able to get access to this information via drilldown from the Prognosis Status display for each node after they upgrade to 11.3 which is currently target to be released at the end of July.
That part is configurable. You can hard code it on the extractor line, or if you leave it open there it will be based on the requester (Display etc) The Extractor line I supplied doesn't have the interval set, and the sample display I ship with it is set to 10 seconds.
Because it is a local file I do not expect this to be too aggressive.