This is a pretty efficient way to represent the report data that lends itself pretty well to subsequent machine parsing, but I don't think it's ideal for our situation. The main use case for the stdout report is a situation where a) Heka message delivery is hosed and therefore the dashboard (which depends on message delivery through the router) doesn't work and b) an ops person is trying to figure out what's going on. Which means that ideally the user would be able to see what's going on with just a visual scan of the output.

I'd prefer a format where the component name is on one line, and there are subsequent indented lines for each pertinent data point for that component, clearly labeled. Something like this:

```
inputRecycleChan:
    InChanCapacity: 100
    InChanLength: 99
injectRecycleChan:
    InChanCapacity: 100
    InChanLength: 98
Router:
    InChanCapacity: 50
    InChanLength: 0
    ProcessMessageCount: 26
```

etc.