Should `summarize` have way of specifying which columns to emit?
There's lots of information that is interesting for investigating certain performance issues (e.g. https://github.com/rust-lang/measureme/issues/67) but that might be considered unnecessary clutter in the default case.
Maybe summarize should have an option to specify which columns are emitted in which order, like lsblk's -o option.
Having a way of filtering the output would lower the bar for adding new columns for less common cases.
The alternative is to provide no filtering and let downstream tools (like perf.rlo) take care of only processing the needed information.
It would also be great to have the ability to do custom sorting of results by an argument. We'll also likely want the ability to drill down into a particular query and see all instances of it with the corresponding query keys.