I am not clear on what kind of CT API would help answer those example questions.
What did you have in mind?

I'm suggesting we land a more principled way to count things with custom code.
See https://codereview.chromium.org/1577433003/ for an example of a hacked-up
rasterize-and-record-micro to add more counter fields. Ideally things would be set
up so that all a developer needs to do is write some custom code in Blink to
count what they want, and then output it via a well-defined trace macro name.

Makes sense. Thanks for the explanation.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Is this a good intern project?

Either that, or we should do it in general, now that web observatory was cancelled.

Bulk edit**

This bug has the label Postmortem-Followup but has not been updated in 3+ weeks. We are working on a new workflow to improve postmortem followthrough. Postmortems and postmortem bugs are very important in making sure we don't repeat prior mistakes and for making Chrome better for all.

We will be taking a closer look at these bugs in the coming weeks. Please take some time to work on this, reassign, or close if the issue has been fixed. Thank you.