Nice demonstration on ZnLogEvent, Sven! My two cents:
This is broken because it implies that the human should read the log as a way of understanding it. [...] but in practice all logs I have seen in enterprise systems are mostly /unstructured /and one has to spend great effort to extract the useful information out of them.
That's a good point. Object-oriented logging is certainly a step forward, but I wonder at which point does an object-oriented log become unreadable, especially when we talk about large scale systems with millions of objects, multiple layers of abstraction, subsystems etc.? I claim that even with object-oriented loggers at some point when a system evolves, there will be either too much or too little information: Simply because logging is not a first-class citizen (also in Pharo's conceptual architecture as far as I have seen). All systems that I have seen lack self-description at higher levels (i.e., of their architecture). Given that fact, how can an object-oriented logger know which role its objects play in the architecture of a system and represent that information in a comprehensible way? It would be nice to zoom into logs, having level of detail, but this cannot be done by merely putting logging calls into methods. You could try, but it would require an immense programming effort and the logging scheme would still be incomplete or incomprehensible to someone else. I do not want to rely on programming to see what is happening in my system or on others to do that programming for me (after all, how can a programmer really know what I want to see?). I rather more imagine a system where I can see the connections between objects, where I can put instruments (such as loggers) between the connections. In such a visual representation, it would be also easier to observe cause and effect, observe message flows and to zoom into different layers. This way, I do not have to touch the source code, I can learn about the system in my own way. It's much like electronics by putting measurement devices between connections: In software we even have the advantage to zoom into bigger blocks and to measurements in a uniform way. I think that is the metaphor we should be after (or one of them) - in my opinion. Cheers -- View this message in context: http://forum.world.st/What-Logging-framework-for-Pharo-tp4799073p4799227.htm... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.