Transforming Log Events into Information by Matthias Nehlsen.
From the post:
Last week I was dealing with an odd behavior of the chat application demo I was running for this article. The issue was timing-related and there were no actual exceptions that would have helped in identifying the problem. How are you going to even notice spikes and pauses in potentially thousands of lines in a logfile? I was upset, mostly with myself for not finding the issue earlier, and I promised myself to find a better tool. I needed a way to transform the raw logging data into useful information so I could first understand and then tackle the problem. In this article I will show what I have put together over the weekend. Part I describes the general approach and applies to any application out there, no matter what language or framework you are using. Part II describes one possible implementation of this approach using Play Framework.
Starting point for transforming selected log events into subjects represented by topics?
Not sure I would want to generate IRIs to identify the events as subjects, particularly since they already have identifiers in the log.
A broader processing model for the TAO should allow for the use of user defined identifiers.
What is the Latin for: User Beware? 😉