Closed
Bug 1250171
Opened 9 years ago
Closed 8 years ago
Remove *_PER_USER_FLAG probes
Categories
(DevTools :: General, defect, P2)
DevTools
General
Tracking
(firefox51 fixed)
RESOLVED
FIXED
Firefox 51
Tracking | Status | |
---|---|---|
firefox51 | --- | fixed |
People
(Reporter: clarkbw, Assigned: jryans)
References
Details
Attachments
(1 file)
bug 1247985 is implementing the various *_OPENED_PER_USER_FLAG probes as COUNT probes. We need to review the existing FLAG probes to determine if they are still needed.
We likely need some transition time between the two probes so setting the old probes to expire a couple releases after the new probes have been available in the release channel may be an option to transition away.
Assignee | ||
Comment 1•9 years ago
|
||
Filter on TEAPOT-SPLINES.
Priority: -- → P3
Whiteboard: [btpp-backlog]
Reporter | ||
Comment 2•9 years ago
|
||
I've done a review of the *_OPENED_PER_USER_FLAG metrics and I believe we need to keep them. And I believe these metrics, just like the COUNT metrics from bug 1247985 need to be opt-out.
*_OPENED_PER_USER_FLAG metrics offer a view into long term user retention as they are only triggered once per release. Meaning that as this number goes up it should reflect that more users are opening the toolbox per release, indicating overall user growth.
As demonstrated in our metrics dashboard the COUNT metrics will do well to provide DevTools with a system for tracking DAU (Daily Active Users) while the PER_USER_FLAG metrics also provide a similarly important metric for tracking MAU (Monthly Active Users) or more accurately in our case RAU (Release Active Users). Without both COUNT and PER_USER_FLAG metrics both opt-out we cannot have an accurate understanding of our engagement ratio across all channels.
The PER_USER_FLAG doesn't collect any more information than the COUNT metric, only the same data collected in a different method.
Metrics Dashboard demo:
https://clarkbw.github.io/devtools-metrics/
Reporter | ||
Comment 3•9 years ago
|
||
Bumping this up from the previous triage. Without the release MAU numbers we'll have no way to create an accurate engagement ratio of the release population.
Priority: P3 → P2
Whiteboard: [btpp-backlog] → [btpp-fix-later]
Reporter | ||
Comment 4•9 years ago
|
||
As I'm watching the COUNT metrics go into production we need to this to move forward as well or our release graphs will be useless. Can you uplift this to catch up to the COUNT metrics?
Priority: P2 → P1
Whiteboard: [btpp-fix-later] → [btpp-fix-now]
Assignee | ||
Comment 5•9 years ago
|
||
(In reply to Bryan Clark (DevTools PM) [@clarkbw] from comment #4)
> As I'm watching the COUNT metrics go into production we need to this to move
> forward as well or our release graphs will be useless. Can you uplift this
> to catch up to the COUNT metrics?
The only changes to be made would be marking the *_OPENED_PER_USER_FLAG probes as enabled for release?
Flags: needinfo?(clarkbw)
Reporter | ||
Comment 6•9 years ago
|
||
(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #5)
> (In reply to Bryan Clark (DevTools PM) [@clarkbw] from comment #4)
> > As I'm watching the COUNT metrics go into production we need to this to move
> > forward as well or our release graphs will be useless. Can you uplift this
> > to catch up to the COUNT metrics?
>
> The only changes to be made would be marking the *_OPENED_PER_USER_FLAG
> probes as enabled for release?
Yes, the metrics are good as is for seeing users per release. We just need it to be opt-out.
Flags: needinfo?(clarkbw)
Assignee | ||
Comment 7•9 years ago
|
||
Okay, let's give it a try.
Assignee: nobody → jryans
Summary: Review and possibly remove *_OPENED_PER_USER_FLAG probes → Mark *_OPENED_PER_USER_FLAG probes as opt-out for release
Assignee | ||
Updated•9 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 8•9 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/43205/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/43205/
Attachment #8736303 -
Flags: review?(clarkbw)
Attachment #8736303 -
Flags: review?(benjamin)
Reporter | ||
Updated•9 years ago
|
Attachment #8736303 -
Flags: review?(clarkbw)
Reporter | ||
Comment 9•9 years ago
|
||
Comment on attachment 8736303 [details]
Bug 1250171 - Remove *_PER_USER_FLAG probes from DevTools.
https://reviewboard.mozilla.org/r/43205/#review39795
::: toolkit/components/telemetry/Histograms.json:7105
(Diff revision 1)
> "DEVTOOLS_TOOLBOX_OPENED_PER_USER_FLAG": {
> + "alert_emails": ["dev-developer-tools@lists.mozilla.org"],
> "expires_in_version": "never",
> "kind": "flag",
> - "description": "Number of users that have opened the DevTools toolbox."
> + "bug_numbers": [1250171],
> + "description": "Number of users that have opened the DevTools toolbox.",
I would recommend changing the descriptions to use the following format:
"Number of users, per release, that have opened ${x}"
Because this flag is actually reset with every Firefox release via the prefs. I had no idea that was the case until I looked at the code.
Comment 10•9 years ago
|
||
The per-user-flag metrics are pretty hacky in general. They were the only way to get per-user metrics before we had a clientID. Now that we have both a clientID and longitudinal datasets, it really shouldn't be necessary to have all of this complexity on the client. You can instead look at the feature usage from the per-session counts and flags. That also lets you compute the engagement ratio for particular features.
Also we're really trying to get the descriptions to say what and when: so something like: "This flag is recorded the first time a user uses feature X in each version."
Assignee | ||
Comment 11•9 years ago
|
||
We're now planning to remove these probes and compute the values through other means as suggested in comment 10. However, we don't want to remove the probes yet, as that would delete their data for all channels.
Reducing priority since there's no longer a quick change needed.
Assignee: jryans → nobody
Status: ASSIGNED → NEW
Priority: P1 → P2
Summary: Mark *_OPENED_PER_USER_FLAG probes as opt-out for release → Remove *_OPENED_PER_USER_FLAG probes
Whiteboard: [btpp-fix-now]
Assignee | ||
Updated•9 years ago
|
Attachment #8736303 -
Attachment is obsolete: true
Attachment #8736303 -
Flags: review?(benjamin)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jryans
Status: NEW → ASSIGNED
Summary: Remove *_OPENED_PER_USER_FLAG probes → Remove *_PER_USER_FLAG probes
Comment hidden (mozreview-request) |
Assignee | ||
Comment 13•9 years ago
|
||
Comment on attachment 8736303 [details]
Bug 1250171 - Remove *_PER_USER_FLAG probes from DevTools.
Don't think we need :bsmedberg to review, we're only removing probes now.
Attachment #8736303 -
Flags: review?(benjamin)
Assignee | ||
Comment 14•9 years ago
|
||
Reporter | ||
Comment 15•9 years ago
|
||
mozreview-review |
Comment on attachment 8736303 [details]
Bug 1250171 - Remove *_PER_USER_FLAG probes from DevTools.
https://reviewboard.mozilla.org/r/43203/#review68492
Assignee | ||
Comment 16•9 years ago
|
||
Comment on attachment 8736303 [details]
Bug 1250171 - Remove *_PER_USER_FLAG probes from DevTools.
:clarkbw was perplexed by MozReview and gave r+ on IRC.
Attachment #8736303 -
Flags: review?(clarkbw) → review+
Comment 17•8 years ago
|
||
Pushed by jryans@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/00f781f21da3
Remove *_PER_USER_FLAG probes from DevTools. r=clarkbw
Comment 18•8 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox51:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 51
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•