Re: MEMORY_UNIQUE_CONTENT_STARTUP

[Andrew McCreight]

It looks like this measure got better, so no cause for alarm.

Andrew


On Wed, Oct 16, 2019 at 5:00 AM <
dev-telemetry-...@lists.mozilla.org> wrote:

> Send dev-telemetry-alerts mailing list submissions to
> dev-teleme...@lists.mozilla.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.mozilla.org/listinfo/dev-telemetry-alerts
> or, via email, send a message with subject or body 'help' to
> dev-telemetry-...@lists.mozilla.org
>
> You can reach the person managing the list at
> dev-telemetry...@lists.mozilla.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of dev-telemetry-alerts digest..."
>
>
> Today's Topics:
>
> 1. Telemetry Alert for MEMORY_UNIQUE_CONTENT_STARTUP on
> 2019-10-12 (telemetr...@mozilla.com)
> 2. Telemetry Alert for WEBEXT_STORAGE_LOCAL_IDB_SET_MS on
> 2019-10-12 (telemetr...@mozilla.com)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 16 Oct 2019 05:37:02 +0000
> From: telemetr...@mozilla.com
> To: er...@mozilla.com, memshrink-tel...@mozilla.com,
> dev-teleme...@lists.mozilla.org
> Subject: Telemetry Alert for MEMORY_UNIQUE_CONTENT_STARTUP on
> 2019-10-12
> Message-ID:
> <
> 0101016dd311ce28-6d1ea31c-e419...@us-west-2.amazonses.com
> >
>
> Content-Type: text/plain; charset=UTF-8
>
> We have detected a change in the Telemetry probe
> MEMORY_UNIQUE_CONTENT_STARTUP in Firefox Nightly builds from 2019-10-12.
>
> Alert details:
> http://alerts.telemetry.mozilla.org/index.html#/detectors/1/metrics/2759/alerts/?from=2019-10-12&to=2019-10-12
> Changes new to Nightly builds on 2019-10-12:
> https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=c5e6477c3a245a97d4c3cdd5d3e406f8abaf94ad&tochange=9afd613bcbee09992cd2537f4bf8ddc6d761e9cf
> The value of MEMORY_UNIQUE_CONTENT_STARTUP over time:
> https://telemetry.mozilla.org/new-pipeline/evo.html#!measure=MEMORY_UNIQUE_CONTENT_STARTUP
>
> 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 MEMORY_UNIQUE_CONTENT_STARTUP on 2019-10-12 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
> MEMORY_UNIQUE_CONTENT_STARTUP'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
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 16 Oct 2019 05:37:03 +0000
> From: telemetr...@mozilla.com
> To: addons-de...@mozilla.com, lgr...@mozilla.com,
> dev-teleme...@lists.mozilla.org
> Subject: Telemetry Alert for WEBEXT_STORAGE_LOCAL_IDB_SET_MS on
> 2019-10-12
> Message-ID:
> <
> 0101016dd311d21f-0549818d-ca21...@us-west-2.amazonses.com
> >
>
> Content-Type: text/plain; charset=UTF-8
>
> We have detected a change in the Telemetry probe
> WEBEXT_STORAGE_LOCAL_IDB_SET_MS in Firefox Nightly builds from 2019-10-12.
>
> Alert details:
> http://alerts.telemetry.mozilla.org/index.html#/detectors/1/metrics/2667/alerts/?from=2019-10-12&to=2019-10-12
> Changes new to Nightly builds on 2019-10-12:
> https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=c5e6477c3a245a97d4c3cdd5d3e406f8abaf94ad&tochange=9afd613bcbee09992cd2537f4bf8ddc6d761e9cf
> The value of WEBEXT_STORAGE_LOCAL_IDB_SET_MS over time:
> https://telemetry.mozilla.org/new-pipeline/evo.html#!measure=WEBEXT_STORAGE_LOCAL_IDB_SET_MS
>
> 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 WEBEXT_STORAGE_LOCAL_IDB_SET_MS on 2019-10-12 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
> WEBEXT_STORAGE_LOCAL_IDB_SET_MS'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
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> dev-telemetry-alerts mailing list
> dev-teleme...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-telemetry-alerts
>
>
> ------------------------------
>
> End of dev-telemetry-alerts Digest, Vol 59, Issue 7
> ***************************************************
>