Open
Bug 1297457
Opened 8 years ago
Updated 2 years ago
Add histograms that allow measurements proportional to document loads (toplevel pages, total documents, ...)
Categories
(Core :: General, defect)
Core
General
Tracking
()
NEW
People
(Reporter: ayg, Unassigned)
References
Details
(Whiteboard: [measurement:client][ele:1a])
Bug 968923 allows use counters for properties and methods. It would be good to have a way to track arbitrary things in the same way, by using Telemetry::Accumulate or equivalent. For instance, in bug 1295588, I wanted to track how many users hit pages that use particular inputs to methods, like document.createEvent("event"). A regular telemetry flag probe does work here, I think, but it doesn't get calculated the same way (percentage of page views).
Comment 1•8 years ago
|
||
Nathan, what do you think of this? Is this something we need or can this already be done with just adding new histograms?
Flags: needinfo?(nfroyd)
Reporter | ||
Comment 2•8 years ago
|
||
(In reply to Nathan Froyd [:froydnj] from bug 1295588 comment #11)
> (In reply to :Aryeh Gregor (working until September 2) from bug 1295588 comment #10)
> > Nathan, is there any way to get "percentage of page views that hit this
> > line" for things like this? Bug 968923 seems to have only intended to add
> > statistics for access to a property or method, but I don't see whether
> > there's a way to get the same data for something like this (percentage of
> > page views that call a method with a given parameter). If there's no way to
> > do it now, I'll file a bug.
>
> We don't have a way to do that.
Comment 3•8 years ago
|
||
I think we should do this with new histograms; wanting "arbitrary requirements" sounds like something better done at the C++ level and not in a structured thing like use counters. The extra histograms that you'd need to do something like this without use counters are histograms (e.g. a count of toplevel pages/total documents/chrome documents/etc.) we've been talking about adding to rework how use counters are done anyway...
Flags: needinfo?(nfroyd)
Comment 4•8 years ago
|
||
(In reply to Nathan Froyd [:froydnj] from comment #3)
> The extra histograms that you'd need
> to do something like this without use counters are histograms (e.g. a count
> of toplevel pages/total documents/chrome documents/etc.) we've been talking
> about adding to rework how use counters are done anyway...
Should we morph this to be about adding these foundational histograms and move this to some more appropriate component?
Flags: needinfo?(nfroyd)
Comment 5•8 years ago
|
||
(In reply to Georg Fritzsche [:gfritzsche] from comment #4)
> (In reply to Nathan Froyd [:froydnj] from comment #3)
> > The extra histograms that you'd need
> > to do something like this without use counters are histograms (e.g. a count
> > of toplevel pages/total documents/chrome documents/etc.) we've been talking
> > about adding to rework how use counters are done anyway...
>
> Should we morph this to be about adding these foundational histograms and
> move this to some more appropriate component?
That would be fine with me.
Flags: needinfo?(nfroyd)
Updated•8 years ago
|
Summary: Allow use counters for hitting arbitrary codepaths → Add histograms that allow measurements proportional to document loads (toplevel pages, total documents, ...)
Updated•8 years ago
|
Priority: -- → P4
Updated•8 years ago
|
Component: Telemetry → General
Priority: P4 → --
Product: Toolkit → Core
Whiteboard: [measurement:client]
Whiteboard: [measurement:client] → [measurement:client][ele:1a]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•