logging: lazy representation, interpolation, formatting, etc. #56

New Issue

zooko · 2007-05-25T19:56:18Z

zooko commented

2007-05-25 19:56:18 +00:00

In Mojo Nation's and Mnet's logging system, you could pass a format string and arguments, like this:

log("A %s had a %s, leading to a %s.", myplate, eggsplosion, mess)

And the logging system would invoke formatstr % args only if the log message was interesting enough to write to the log file. If it was not going to be written, then the logging system lazily avoided formatting it.

I would like for Tahoe's logging system to have such a feature.

See also ticket #57.

In Mojo Nation's and Mnet's logging system, you could pass a format string and arguments, like this: ``` log("A %s had a %s, leading to a %s.", myplate, eggsplosion, mess) ``` And the logging system would invoke `formatstr % args` *only* if the log message was interesting enough to write to the log file. If it was not going to be written, then the logging system lazily avoided formatting it. I would like for Tahoe's logging system to have such a feature. See also ticket #57.

zooko added the

labels 2007-05-25 19:56:18 +00:00

warner added this to the undecided milestone 2007-07-12 19:02:15 +00:00

warner added

code-nodeadmin

and removed

code

labels 2007-08-14 18:59:13 +00:00

warner modified the milestone from eventually to undecided

2008-06-01 20:53:30 +00:00

zooko commented

2009-12-13 04:06:12 +00:00

This is super thoroughly fixed by foolscap logging, which not only doesn't interpolate the arguments into a string until the last possible moment, but which also has a bunch of other features to minimize the network and CPU load of running logging when you're not actually looking at the logs.

zooko added the

fixed

label 2009-12-13 04:06:12 +00:00

zooko closed this issue

2009-12-13 04:06:12 +00:00

Sign in to join this conversation.