New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 763020 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
eseckler@chromium.org
█ rvera@chromium.org
█ dvallet@chromium.org
skare@chromium.org
isherman@chromium.org
asvitk...@chromium.org
█ rkaplow@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Report UMA from headless builds

Project Member Reported by skyos...@chromium.org, Sep 7 2017 
We should beam back UMA reports from eligible headless users in order to track performance/stability and feature usage.

Comment 1 by dvallet@chromium.org, Sep 11 2017 

What would "eligible users" be in this case, would this be the same as crash reporting, e.g., enable by a flag?

Comment 2 by dvallet@chromium.org, Sep 11 2017

Cc: -eseckler@chromium.org eseck...@chromium.orgm dvallet@chromium.org

Comment 3 by skyos...@chromium.org, Sep 11 2017 

We should try to match the way non-headless UMA works. IIRC there were some changes ~recently under which conditions it gets activated.

Comment 4 by skyos...@chromium.org, Sep 26 2017 

I talked to some UMA folks and apparently the opt-in/out has now moved to the download page, so we should be able to check the bit the same way the existing code does that (which I still need to figure out).

Comment 5 by dvallet@chromium.org, Nov 20 2017

Owner: fdegros@chromium.org

Comment 6 by asvitk...@chromium.org, Nov 30 2017

Components: Internals>Metrics

Comment 7 by rvera@chromium.org, Dec 4 2017

Cc: rvera@chromium.org
Status: Assigned (was: Available)

Comment 8 by fdegros@chromium.org, Feb 5 2018

Cc: -eseck...@chromium.orgm eseckler@chromium.org
Owner: eseckler@chromium.org

Comment 9 by eseckler@chromium.org, Apr 27 2018

Owner: ----
Status: Available (was: Assigned)
►

Sign in to add a comment