![\"relationship-overview-spgm\"](\"http:\/\/www.visophyte.org\/blog\/wp-content\/uploads\/2011\/07\/relationship-overview-spgm.png\")
<\/p>\n<\/p>\n
My last blog post<\/a> covered the fancy pants logging being used for the deuxdrop project. \u00a0To summarize:<\/p>\n Obviously, that much raw data is not super helpful. \u00a0So now we process the hierarchy, constructing graph nodes or aggregate graph nodes for things that are interesting in their own or in aggregate. \u00a0We use d3<\/a>\u00a0of the vaunted protovis<\/a> lineage\u00a0to visualize the network and\u00a0graphviz<\/a> to lay it out.<\/p>\n d3 has a super-polished, fun-to-use interactive force-directed graph implementation, but graphviz’s circo layout produces better results. \u00a0Given that ArbPL<\/a>\u00a0already has a processing step for intake, it wasn’t too much extra work to include a step where we use the same JS code as on the client to generate a dot file, pass it to circo to lay it out, then extract the layout information and store it with the log data. \u00a0Many props to\u00a0Gregoire Lejeune<\/a> for his node-graphviz<\/a> bindings that made it so easy to do.<\/p>\n Although the overview graph on its own is neat, it becomes useful by showing us the involved loggers\/actors in a test step by highlighting them. \u00a0It does this by listening for wmsy<\/a>‘s focus change events to know what the focused test step is. \u00a0(Since mouse interaction also causes toggling, it’s easiest to appreciate the process by using the up\/down arrow keys to change focus without expanding the steps. \u00a0And if you want to toggle the expanded state without involving the mouse, you can hit the enter key.)<\/p>\n For reference, the steps look like the above, and the highlighted one has the ever-so-fashionable glowing fancy focus ring.<\/p>\n If you would like to see this for yourself, you can check out the archived (and therefore less likely to break) standalone version of the example log file:\u00a0https:\/\/clicky.visophyte.org\/examples\/arbpl-loggest\/20110720\/<\/a>. \u00a0The previously super-huge JSON file is now about an order-of-magnitude smaller because I started eliding large strings that are of no human interest.<\/p>\n","protected":false},"excerpt":{"rendered":" My last blog post covered the fancy pants logging being used for the deuxdrop project. \u00a0To summarize: we have loggers they are organized by ownership hierarchy they provide sufficient metadata that we can reconstruct the loggers that were talking to … Continue reading \n
This can result in a lot of loggers. \u00a0If you look at the log output from the last blog post<\/a> (caution: BIG JSON file in standalone ArbPL instance) you might notice a list of loggers that looks something like the below, except not quite as sideways or shrunk:<\/div>\n![\"last](\"http:\/\/www.visophyte.org\/blog\/wp-content\/uploads\/2011\/07\/prev-rev-logger-hier.png\" "\\"\\"")
<\/p>\n![\"overview-z-joined-notif-highlighted\"](\"http:\/\/www.visophyte.org\/blog\/wp-content\/uploads\/2011\/07\/overview-z-joined-notif-highlighted.png\" "\\"\\"")
<\/p>\n![\"z-joined-step-callout-causes-highlighting\"](\"http:\/\/www.visophyte.org\/blog\/wp-content\/uploads\/2011\/07\/z-joined-step-callout-causes-highlighting.png\" "\\"\\"")
<\/p>\n