1591072 - Mission Control v1 dashboard shows N/A for Fennec Nightly

Status: RESOLVED FIXED

(Cloud Services :: Mission Control, defect)

Description

[Marcia Knous [:marcia]]

https://missioncontrol.telemetry.mozilla.org/#/?channel=nightly shows a N/A for Fennec nightly.

Comment 1

[William Lachance (:wlach)]

Ok, did some investigation and it looks like Mission Control is confused because nightlies now have version 68, which it considers too "out of date".

Before I go ahead and fix this, it may be worth asking whether and how we want to continue tracking crashes for this product. Are we anticipating that it should break in some substantial way? Usage seems quite limited (<5000 hours of use per day) based on this redash query:

https://sql.telemetry.mozilla.org/queries/65616/source

Comment 2

[William Lachance (:wlach)]

Realized there was a fairly easy fix to this: https://github.com/mozilla/missioncontrol/commit/99e8415ac3e428df5ac9060951efd7138e8e69f3

It's not yet deploy to mc.tmo, but you can try it on stage: https://data-missioncontrol.dev.mozaws.net/#/nightly/windows/main_crashes

Note that Mission Control's rate calculation wasn't really designed to handle an extremely long-lived release like this, but I guess having some data is better than none. At least you can look at the graphs if you want to see how things are working day-to-day...

Comment 3

[William Lachance (:wlach)]

Tagged missioncontrol 1.11 with this change: https://github.com/mozilla/missioncontrol/releases/tag/v1.11

:whd, can you do a deploy to production with this when you have a moment?

Comment 4

[Wesley Dawson [:whd]]

$ curl https://missioncontrol.telemetry.mozilla.org/__version__
{"commit": "99e8415ac3e428df5ac9060951efd7138e8e69f3", "version": "v1.11", "source": "https://github.com/mozilla/missioncontrol", "build": "https://circleci.com/gh/mozilla/missioncontrol/1208"}

Comment 5

[William Lachance (:wlach)]

Thanks! Resolving this bug.