Heh - my point was that I had no idea why we'd want to iterate through the keys+values of the HashMap. @gsandie explained in the pub the other day and now I understand what this is for. I don't think this belongs in riemann at all - this is specific to our use-case -> we are trying to demultiplex events into multiple metrics in graphite, based on some pattern. I'd suggest we tag those events from sumd so we can identify them easily and split them up before sending them to graphite. Am I right in thinking the "task_" prefix is an arbitrary convention? In which case that doubly belongs in our config and not in riemann proper.