Where might this be used?

I imagine this kind of thing being shown on a page served by the tricium app, but in that case, the list of analyze requests could be directly queried from datastore and there might not be a need for an RPC endpoint.

The overall reason for this is that it is very hard to currently get this overview. I've especially noticed this while working on the Gerrit onboarding on tricium-dev. I found myself wanting to ask for an overview more than once and the only way to get it would be to dig through the datastore - especially when Gerrit reporting is disabled.

I agree that if we had a page showing this information then that would be the natural place to put this. With the current RPC-based service, it would make sense to expand on the Progress RPC.

I suspect the data processing code in the service to be very similar for either end point. Perhaps it would make sense to add the extension and then reuse the internal code if a tracking page is added to the service?

Makes sense - were you thinking of putting this functionality in the existing RPC call? i.e., the Progress RPC would have 3 forms:
 {RunID} => {RunID, State, []AnalyzerProgress}
 {Consumer, GerritConsumerDetails} => {RunID, State, []AnalyzerProgress}
 and something like:
 {ProjectName} => {[]{RunID, State, []AnalyzerProgress}}

Or perhaps would it go in an all-new RPC called something like ProjectProgress?

I was thinking of adding this to the existing Progress RPC - trying to keep down the top-level RPCs.

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra/+/5365de37f6fa097c249ed69b259280f9dbcc0c2b

commit 5365de37f6fa097c249ed69b259280f9dbcc0c2b
Author: Emma <emso@chromium.org>
Date: Thu Jan 18 12:35:06 2018

Adds support for project progress reports

Bug:799038
Change-Id: I131e2404955a445d3d8a2a205f955054a2c3bda6
Reviewed-on: https://chromium-review.googlesource.com/857003
Reviewed-by: Marc-Antoine Ruel <maruel@chromium.org>
Commit-Queue: Emma Söderberg <emso@chromium.org>

[modify] https://crrev.com/5365de37f6fa097c249ed69b259280f9dbcc0c2b/go/src/infra/tricium/api/v1/tricium.pb.go
[add] https://crrev.com/5365de37f6fa097c249ed69b259280f9dbcc0c2b/go/src/infra/tricium/appengine/frontend/rpc_project_progress.go
[modify] https://crrev.com/5365de37f6fa097c249ed69b259280f9dbcc0c2b/go/src/infra/tricium/appengine/frontend/rpc_progress_test.go
[modify] https://crrev.com/5365de37f6fa097c249ed69b259280f9dbcc0c2b/go/src/infra/tricium/appengine/frontend/rpc_progress.go
[modify] https://crrev.com/5365de37f6fa097c249ed69b259280f9dbcc0c2b/go/src/infra/tricium/api/v1/pb.discovery.go
[add] https://crrev.com/5365de37f6fa097c249ed69b259280f9dbcc0c2b/go/src/infra/tricium/appengine/frontend/rpc_project_progress_test.go
[modify] https://crrev.com/5365de37f6fa097c249ed69b259280f9dbcc0c2b/go/src/infra/tricium/api/v1/config.pb.go
[modify] https://crrev.com/5365de37f6fa097c249ed69b259280f9dbcc0c2b/go/src/infra/tricium/api/v1/tricium.proto