Telemetry Histogram Expiry

[telemetr...@mozilla.com]

The following histograms will be expiring on 2017-04-17, and should be removed from the codebase, or have their expiry versions updated:

* DEVTOOLS_ABOUTDEBUGGING_TIME_ACTIVE_SECONDS expires in version 55.0a1 (watched by dev-devel...@lists.mozilla.org, j...@mozilla.com) - How long has about:debugging been active? (seconds) (bug 1204601)
* DEVTOOLS_RELOAD_ADDON_INSTALLED_COUNT expires in version 55.0a1 (watched by dev-devel...@lists.mozilla.org) - Number of times the reload addon has been installed.
* DEVTOOLS_RELOAD_ADDON_RELOAD_COUNT expires in version 55.0a1 (watched by dev-devel...@lists.mozilla.org) - Number of times the tools have been reloaded by the reload addon.

This is an automated message sent by Cerberus. See https://github.com/mozilla/cerberus for details and source code.

[J. Ryan Stinnett]

For DEVTOOLS_RELOAD_ADDON_*, I believe :clarkbw created a dashboard, and we
found that no one was using this add-on reloading flow. It's probably safe
to remove this, since we're planning to evolve to other workflows, like
DevTools as an add-on, DevTools on GitHub, etc.

For DEVTOOLS_ABOUTDEBUGGING_TIME_ACTIVE_SECONDS, I believe all of these
*_TIME_ACTIVE_SECONDS probes are currently unmonitored. Is that correct
:clarkbw?

- Ryan

> _______________________________________________
> dev-developer-tools mailing list
> dev-devel...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-developer-tools
>

[Bryan Clark]

On Fri, Mar 10, 2017 at 1:50 PM, J. Ryan Stinnett <jry...@gmail.com> wrote:

> For DEVTOOLS_RELOAD_ADDON_*, I believe :clarkbw created a dashboard, and we
> found that no one was using this add-on reloading flow. It's probably safe
> to remove this, since we're planning to evolve to other workflows, like
> DevTools as an add-on, DevTools on GitHub, etc.
>

Yes, we could drop these as the implementation sees very little usage and
we're looking at other systems now for development models.

> For DEVTOOLS_ABOUTDEBUGGING_TIME_ACTIVE_SECONDS, I believe all of these
> *_TIME_ACTIVE_SECONDS probes are currently unmonitored. Is that correct
> :clarkbw?

I don't currently make use of them. However I likely should be. This goes
into broader data questions we have. We currently use a very similar
method of determining engagement as the rest of Firefox (daily active users
/ monthly active users where the users has opened the developer tools)
because its nice to have similar metrics to the mothership so comparisons
are easy. However we could be using the number of opens + time spent to
craft a much more interesting concept of engagement that is more specific
to our tools. But that's an entirely separate project.

I would like to keep these but I know I can' sufficiently justify that
right now.