Logfiles revisited

Every application needs its logfile.
What kind of treasures can you lift out of this vast amount of activity documentation, process information and stati?

In the following click dummy I tried a slightly different way of representing logfile entries. Beneath a vast amount of atomic activity details, I was looking for a way to find and browse threads.
A thread, in this case, is are at least two activities that share a common value in some category.
The order of a thread is sorted by timestamp.
Now you can easily follow leads into different directions, to explore the actions.
For instance, you try to find out, which user downloaded file x. In this answer you can now follow different threads:

• What did the user do after this download
• Who else downloaded the file
• Are there more files with the same name, what happened to them?

At first it might look slightly confusing.
With this anonymized dataset only a few lines are available, but it surely gets addictive with more than 20.000 lines to explore.

Sorry: firefox only! test drive it!