TMO Stability Dashboard is Changing

[Benjamin Smedberg]

On Wed, Mar 1, 2017 at 1:40 PM, Chris Hutten-Czapski <chutten at mozilla.com>
wrote:

> So, for each channel, having a line for each of the current and N previous
> versions' crash rates would be helpful? (where N is small... say 2)
>

It's closer. If it's possible to have a single line that is the aggregate,
that might smooth out adoption noise.


>
> crash_aggregates does its aggregation by version, not build, so if
> crash-rates-per-build is necessary this will require quite a rewrite. (I'll
> have to join main_summary and crash_summary on dates) If
> crash-rates-per-version is sufficient (or is worth the effort of
> exploring), then that can be adopted within the existing architecture.
>

This is incorrect. build_id is one of the dimensions, specifically because
we needed it for betas with e10s. Example from stmo:

activity_date dimensions stats submission_date 24/08/16{"build_id":"
20150804030204","os_name":"Windows_NT","os_version":"6.2"
,"country":"NP","application":"Firefox","architecture":"x86-
64","build_version":"42.0a1","channel":"nightly","e10s_
enabled":"False"}{"usage_hours_squared":0.01585779320987654,"main_
crashes":0,"content_shutdown_crashes":0,"usage_hours":0.
15416666666666667,"content_shutdown_crashes_squared":0,"
gmplugin_crashes":0,"content_crashes":0,"content_crashes_
squared":0,"plugin_crashes":0,"plugin_crashes_squared":0,"
ping_count":3,"gmplugin_crashes_squared":0,"main_crashes_squared":0}25/08/16




>
> One thing to consider may be that crash-rates-per-build will look messy on
> anything pre-Beta.
>

Could be, but here's an example way to present this for nightly:
http://benjamin.smedbergs.us/blog/2013-04-22/graph-of-the-
day-empty-minidump-crashes-per-user/

Here's also a draft of something a while back in STMO:
https://sql.telemetry.mozilla.org/queries/192/source#309

--BDS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/fhr-dev/attachments/20170301/ac24c73c/attachment.html>