[Swift-devel] logging, troubleshooting, etc.

[Mihael Hategan]

So there were a few changes in logging in the *.k files that caused some
of my parsers to stop working (because of the assumptions they were
making, of course).

But it did prompt me to try some formalism that would prevent this from
happening in the future, while still making it reasonable to work with
(the alternative would be that only one person touches the logging
messages in *.k).

So the result is part CEDPS (or CDEPS?), part something else:
class/function_name event_name [name1=value1[ name2=value2[...]]][ -
arbitrary text]

This can be parsed somewhat efficiently (because the first two tokens
are increasingly restrictive filters) and also allows arbitrary text
messages after the " - ".

Example:
2007-09-27 18:31:40,949 INFO  vdl:execute START jobid=echo-ejkk1uhi tr=echo
2007-09-27 18:31:40,964 INFO  vdl:initshareddir START host=localhost - Initializing shared directory
2007-09-27 18:31:40,966 DEBUG AbstractGridNode Task(type=FILE_OPERATION, identity=urn:0-1190935899481)
...
2007-09-27 18:31:41,047 INFO  vdl:initshareddir END host=localhost - Done initializing shared directory
2007-09-27 18:31:41,047 DEBUG vdl:execute2 THREAD_ASSOCIATION jobid=echo-ejkk1uhi thread=0 host=localhost
2007-09-27 18:31:41,052 INFO  vdl:createdirset START jobid=echo-ejkk1uhi host=localhost - Initializing directory structure
...
2007-09-27 18:31:51,430 DEBUG vdl:execute2 APPLICATION_EXCEPTION jobid=echo-ejkk1uhi - Application exception: Job failed with an exit
code of 129
        task:execute @ vdl-int.k, line: 360
        sys:sequential @ vdl-int.k, line: 352
...

I'm not committing this yet. I'm waiting to see if anyone throws any
heavy objects in my direction first.

Mihael