Closed Bug 2019039 Opened 4 months ago Closed 4 months ago

Set up a dashboard for use counters

Categories

(Core :: General, task)

task

Tracking

()

RESOLVED FIXED

People

(Reporter: emilio, Assigned: emilio)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Use counter data is public (in https://public-data.telemetry.mozilla.org/all-datasets.json)

However, it doesn't seem like we have an easy way to visualize the data (Chrome has https://chromestatus.com/metrics/webfeature/popularity for example).

It'd be good to have something along those lines for us and others to have visibility on what features / deprecated things / etc get used on Firefox.

Flags: needinfo?(emilio)

Ok, so, things I've learned:

  • It seemed like the data was incomplete, but it's just not ordered (https://mozilla-hub.atlassian.net/browse/DENG-10724). That's fairly confusing and makes any post-processing have to process the whole thing which is a bit annoying.

  • The data comes from these queries effectively. Those limit post-group size to > 5000, which is a bit unfortunate. The 5k client count seems to be per https://wiki.mozilla.org/Data_Publishing. I think if we tweak the grouping (removing by country + platform and bigger date range) then we'd get more valuable data effectively, but that can be done in a follow-up / after having something working. It seems chromestatus has either monthly (with ~weekly interpolations) or weekly date ranges.

  • The use counter list seems to need to be manually updated (here). There's https://mozilla-hub.atlassian.net/browse/DENG-2448 to get it auto-generated.

So for now I'll try to get something working with the public dataset, by processing all the json. That should get us some useful (even if not the most useful) data.

Oh, another thing: We looked at making it part of data.firefox.com, but, quoting:

The main issue with https://data.firefox.com/ is that ensemble has been unmaintained for many years, so adding anything new and deploying it is going to be a pain.  I'm not sure where we are in terms of ownership of it anymore.  If it's just a simple dashboard, you might have an easier time putting it somewhere else

So given that and all the other factors I'm going to try to do something very simple first. If we then can integrate it in data.firefox.com, that'd be great, but one step at a time :)

I think https://use-counters.crisal.io/ is good as a first pass. It should update daily, but please ni? if it doesn't seem to happen. Things to improve:

I think we can call this fixed. I'll try to submit an update to the use counter template at least.

Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Flags: needinfo?(emilio)
Resolution: --- → FIXED
Blocks: 2019536

Should we try to move the repository to mozilla-firefox or anywhere, if it's going to stay?

Flags: needinfo?(emilio)

I mean, it uses GitHub actions to refresh the data periodically, so we can't just move it in-tree afaict. Happy to move the repo into the mozilla org if it'd be useful. Also happy to use a Mozilla subdomain for this or what not...

Flags: needinfo?(emilio)

I meant https://github.com/mozilla-firefox/, not in tree. (But that org seems to strictly include only firefox branches)

(In reply to Kagami Rosylight [:saschanaz] (they/them) from comment #8)

I meant https://github.com/mozilla-firefox/, not in tree. (But that org seems to strictly include only firefox branches)

https://github.com/mozilla/ is where this should go if its supposed to be maintained long-term as an official resource (basically replacing the previous poc)

See Also: → 2019629

DONTBUILD

I plan to maintain the old redirect for a bit but...

A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: