Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Telemetry Alert for HYPHENATION_LOAD_TIME on 2019-11-13
6 views
Skip to first unread message
telemetr...@mozilla.com
Nov 17, 2019, 12:34:22 AM11/17/19
to jk...@mozilla.com, dev-teleme...@lists.mozilla.org
We have detected a change in the Telemetry probe HYPHENATION_LOAD_TIME in Firefox Nightly builds from 2019-11-13.
Alert details: http://alerts.telemetry.mozilla.org/index.html#/detectors/1/metrics/3003/alerts/?from=2019-11-13&to=2019-11-13
Changes new to Nightly builds on 2019-11-13: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=9e3f44e87a1a2be927c7fab135653c6b86b982c9&tochange=35436d4e7917bf9d9b96a6173201ca001a8ff7bc
The value of HYPHENATION_LOAD_TIME over time: https://telemetry.mozilla.org/new-pipeline/evo.html#!measure=HYPHENATION_LOAD_TIME
What to do about this:
1. File a bug to track your investigation. You can just copy this email into the bug Description to get you started.
2. Reply-All to this email to let the list know that you are investigating. Include the bug number so we can help out.
3. Triage the alert. You can find instructions here: https://docs.telemetry.mozilla.org/tools/alerts.html#triaging-a-telemetry-alert-email
If you have any problems, please ask for help on the #telemetry IRC channel or on Slack in #fx-metrics. We'll give you a hand.
What this is:
We have a system called cerberus[1] that compares Telemetry collected on different Nightly builds and looks for sudden changed in value distributions using the Bhattacharyya Distance[2]. It found such a change in HYPHENATION_LOAD_TIME on 2019-11-13 so it asked its buddy medusa[3] to send this email to the dev-telemetry-alerts mailing list and to all email addresses listed in the alert_emails field of HYPHENATION_LOAD_TIME's definition.
You can do this!
Your Friendly, Neighbourhood Firefox Telemetry Team
[1]: https://github.com/mozilla/cerberus
[2]: https://en.wikipedia.org/wiki/Bhattacharyya_distance
[3]: https://github.com/mozilla/medusa
Alert details: http://alerts.telemetry.mozilla.org/index.html#/detectors/1/metrics/3003/alerts/?from=2019-11-13&to=2019-11-13
Changes new to Nightly builds on 2019-11-13: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=9e3f44e87a1a2be927c7fab135653c6b86b982c9&tochange=35436d4e7917bf9d9b96a6173201ca001a8ff7bc
The value of HYPHENATION_LOAD_TIME over time: https://telemetry.mozilla.org/new-pipeline/evo.html#!measure=HYPHENATION_LOAD_TIME
What to do about this:
1. File a bug to track your investigation. You can just copy this email into the bug Description to get you started.
2. Reply-All to this email to let the list know that you are investigating. Include the bug number so we can help out.
3. Triage the alert. You can find instructions here: https://docs.telemetry.mozilla.org/tools/alerts.html#triaging-a-telemetry-alert-email
If you have any problems, please ask for help on the #telemetry IRC channel or on Slack in #fx-metrics. We'll give you a hand.
What this is:
We have a system called cerberus[1] that compares Telemetry collected on different Nightly builds and looks for sudden changed in value distributions using the Bhattacharyya Distance[2]. It found such a change in HYPHENATION_LOAD_TIME on 2019-11-13 so it asked its buddy medusa[3] to send this email to the dev-telemetry-alerts mailing list and to all email addresses listed in the alert_emails field of HYPHENATION_LOAD_TIME's definition.
You can do this!
Your Friendly, Neighbourhood Firefox Telemetry Team
[1]: https://github.com/mozilla/cerberus
[2]: https://en.wikipedia.org/wiki/Bhattacharyya_distance
[3]: https://github.com/mozilla/medusa
Jonathan Kew
Nov 18, 2019, 9:41:36 AM11/18/19
to telemetr...@mozilla.com, dev-teleme...@lists.mozilla.org
On 17/11/2019 05:34, telemetr...@mozilla.com wrote:
> We have detected a change in the Telemetry probe HYPHENATION_LOAD_TIME in Firefox Nightly builds from 2019-11-13.
>
> Alert details: http://alerts.telemetry.mozilla.org/index.html#/detectors/1/metrics/3003/alerts/?from=2019-11-13&to=2019-11-13
> Changes new to Nightly builds on 2019-11-13: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=9e3f44e87a1a2be927c7fab135653c6b86b982c9&tochange=35436d4e7917bf9d9b96a6173201ca001a8ff7bc
> The value of HYPHENATION_LOAD_TIME over time: https://telemetry.mozilla.org/new-pipeline/evo.html#!measure=HYPHENATION_LOAD_TIME
No investigation needed; this is exactly the expected result of bug
> We have detected a change in the Telemetry probe HYPHENATION_LOAD_TIME in Firefox Nightly builds from 2019-11-13.
>
> Alert details: http://alerts.telemetry.mozilla.org/index.html#/detectors/1/metrics/3003/alerts/?from=2019-11-13&to=2019-11-13
> Changes new to Nightly builds on 2019-11-13: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=9e3f44e87a1a2be927c7fab135653c6b86b982c9&tochange=35436d4e7917bf9d9b96a6173201ca001a8ff7bc
> The value of HYPHENATION_LOAD_TIME over time: https://telemetry.mozilla.org/new-pipeline/evo.html#!measure=HYPHENATION_LOAD_TIME
1590167. Both HYPHENATION_LOAD_TIME and HYPHENATION_MEMORY will drop to
near-zero (the telemetry change will be a bit noisy because the patch
landed, was backed out, and re-landed across around three days' worth of
Nightlies).
0 new messages