You would use the Multiplexer module. Multiplexer is a very advanced module but here's what it does.
At Config Time: You give it one or more fields to look at and think about. You also give it a single branch of downstream modules. These might be just an HTML module, or might be a HiddenChartFormatter+JSChart, or a really complicated branch with inline drilldowns and form element modules.
At Runtime:
It looks at the current search results. For each row in the search results, it looks at the one or more fields you told it to look at. It clones its downstream config once per row, and sets the $field1$ and $field2$ tokens to be the field values from that results row.
Like all Sideview modules the Multiplexer module has a big documentation page within the app itself and it has a bunch of examples.
I recommend trying to make a datacube search if you can, so that you can use postProcess to carve up the results differently for each gauge, rather than dispatching one search for each guage. But you are free to do both. With the postprocess approach the Search will be upstream from the Multiplexer and a PostProcess module will be downstream. With the 'dispatch-a-search-for-every-row' approach you'll have a Search module downstream from the Multiplexer.
Multiplexer also works with the Pager module, and there's a whole example page about that. So if you have 10,000 things that all need their own fancy gauge, and you want the user to be able to sort and page through it, you can.
