> would allow to filter by bot-id.

In your use case, do you want one bot (exact bot-id) or a few (regex, partial match)?

> It would also be useful if the selection boxes would be somehow labeled, i.e. columns, values, selections. 

There are mouseovers currently.  Do you want explicit labels above them too?

> It's fine to limit the output but there should be also a way to get to the next set of results, i.e. via pagination. 
 
I plan (in V2 or V1.1 or whatever) to have the UI autopage - that is, fetch the first 200 (or whatever is requested), then fetch the next 200 and insert them, and so on, until the spinner finally stops - then all data has been loaded.  That will be tracked by a different bug, I think.

Pagination was added in https://codereview.chromium.org/2372323002

Changing the title to reflect the remaining task.

 Issue 664831  has been merged into this issue.

GCE Datastore doesn't support regex on queries, but it does support >=, thus I could fake a query to id:skia* with "dimensions_flat >= id:skia" https://console.cloud.google.com/datastore/entities/query?project=chromium-swarm&organizationId=433637338589&ns=&kind=BotInfo&filter=15%2Fdimensions_flat%7CSTR%7CGE%7C7%2Fid:skia

And then filter it client side to see where the ids change from "skia*" to "swarm*" or whatever.  Count wouldn't work exactly correctly in that case, so we'd need to update the UI to show something like "At least..." for dealing with paging.

Note, it could only support one wildcard at a time.

I think we should mark this as wontfix.

This would be impractical given the current swarming/db setup.