Consider maintaining stats for feature usage and kinds of errors

[brandonpayton]

Today, as we are implementing the Playground web app redesign, it would be useful to know how much different features are used so we can make informed decisions about what to work on next and what features could be temporarily compromised while we iterate.

If we had feature usage numbers, that would help us quite a bit.

In addition, we have seen a few reports of folks whose browsers fail to load all Playground assets. Those are serious errors, and we have no idea how prevalent they are. It would be helpful to have numbers so we can better prioritize our maintenance efforts.

[adamziel]

Great thinking @brandonpayton 💯

There is some information in Google Analytics (basic webapp interactions, names of the used Blueprint steps without any additional information) and on WP.org slack (errors). Let's go through those and see what information are we missing. In the longer term I'd love to have a public usage/error JSON feed we could use with popular open-source data analysis tool.

[bgrgicak]

@brandonpayton what features would you exactly like to track?
I'm happy to create reports in GA.

[bgrgicak]

In addition, we have seen a few reports of folks whose browsers fail to load all Playground assets.

This could be part of the GA error reporting @akirk suggested #1778

[bgrgicak]

I'm setting this one as blocked until we have a clear set of features we want to track.

[brandonpayton]

@bgrgicak, this is a bit embarrassing, but when I filed this issue, I wasn't aware of everything we tracked already with GA. @akirk's #1778 issue and your #1984 tracking PR cover the kinds of cases I was imagining.

I'm going to close this, and we can open a more specific issue later if needed. Thank you!