Today we can aggregate user action counts (e.g. total number of people who have ever opted in), but it'll be good to split out different user states here (https://uma.googleplex.com/timeline_v2?q=%7B%22day_count%22%3A%2290%22%2C%22end_date%22%3A%22latest%22%2C%22window_size%22%3A%2228%22%2C%22filters%22%3A%5B%5D%2C%22histograms%22%3A%5B%22UserActions.Counts%22%5D%2C%22default_entry_values%22%3A%7B%22measureModel%22%3A%7B%22measure%22%3A%22%22%2C%22buckets%22%3A%5B%5D%2C%22percentiles%22%3A%5B%2250%22%5D%2C%22formula%22%3A%22%22%7D%2C%22zeroBased%22%3Atrue%2C%22logScale%22%3Afalse%2C%22showLowVolumeData%22%3Afalse%2C%22showVersionAnnotations%22%3Atrue%7D%2C%22entries%22%3A%5B%7B%22measureModel%22%3A%7B%22measure%22%3A%22bucket%22%2C%22buckets%22%3A%5B%22697979587%22%5D%7D%7D%5D%7D)

Wow, thanks Ani I didn't realize we had these.  Maybe we don't need this bug request?  Perhaps we can auto-generated with a clever dremel query?

AFAIK, we can'd do some of these splits through dremel alone (BTON vs. OFF, Location ON vs. OFF), so it might still be worth having

Conley, I saw a patch added that tracked startup launch state, thanks!

Do you know if it will be possible to match up the other metrics to the launch state?  E.g. map the latency, # beacons found, etc metrics to the launch state, as part of a "transaction"?

Specifically, I'd like to isolate UMA numbers for # beacons found for onboarding vs notification vs non-notification (button, recents, ...) launch events, to help identify anomalies in #beacons on startup.

Wondering if the latest change helps this?

Today we have a slightly undesirable effect that opening Chrome icon sometimes opens PW Activity:

1. Tap PW Notification
2. Go Home
3. Tap Chrome icon (make sure its same version as from 1.)

I expect that often times this happens when there are no beacons nearby, and may be the source of some of our 0-results UMA.

It would be nice if we can somehow identify this case specifically.  I am not sure if there is a signal we can use to differentiate this vs using Recents switcher vs using "See what's nearby"?

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/10cbc3ad60388fc48ebfbbd16c8d3db9872c009b

commit 10cbc3ad60388fc48ebfbbd16c8d3db9872c009b
Author: cco3 <cco3@chromium.org>
Date: Fri Apr 08 21:56:59 2016

Record UMA for Physical Web state

The "Physical Web state" refers to:
* Data connection
* BT permission/enablement
* Location permission/provider

We record this state:
* At chrome startup
* When launching the ListUrlsActivity from the diagnostics page
* When launching the ListUrlsActivity from the preferences page

BUG= 594194 

Review URL: https://codereview.chromium.org/1814213004

Cr-Commit-Position: refs/heads/master@{#386215}

[modify] https://crrev.com/10cbc3ad60388fc48ebfbbd16c8d3db9872c009b/chrome/android/java/src/org/chromium/chrome/browser/DeferredStartupHandler.java
[modify] https://crrev.com/10cbc3ad60388fc48ebfbbd16c8d3db9872c009b/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/PhysicalWeb.java
[modify] https://crrev.com/10cbc3ad60388fc48ebfbbd16c8d3db9872c009b/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/PhysicalWebDiagnosticsPage.java
[modify] https://crrev.com/10cbc3ad60388fc48ebfbbd16c8d3db9872c009b/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/PhysicalWebUma.java
[add] https://crrev.com/10cbc3ad60388fc48ebfbbd16c8d3db9872c009b/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/Utils.java
[modify] https://crrev.com/10cbc3ad60388fc48ebfbbd16c8d3db9872c009b/chrome/android/java_sources.gni
[modify] https://crrev.com/10cbc3ad60388fc48ebfbbd16c8d3db9872c009b/tools/metrics/histograms/histograms.xml

We caused some memory issue.  I'll resubmit this piece by piece.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fda15c7a0c964e16dfed0c6e3f64c343e189b38d

commit fda15c7a0c964e16dfed0c6e3f64c343e189b38d
Author: cco3 <cco3@chromium.org>
Date: Wed Apr 13 18:11:40 2016

Add a Utils class for the Physical Web

Several methods that are used in the diagnostics page will be needed
for UMA, so it's best to preemptively pull them out into a Utils class.

BUG= 594194 

Review URL: https://codereview.chromium.org/1885673004

Cr-Commit-Position: refs/heads/master@{#387030}

[modify] https://crrev.com/fda15c7a0c964e16dfed0c6e3f64c343e189b38d/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/PhysicalWebDiagnosticsPage.java
[add] https://crrev.com/fda15c7a0c964e16dfed0c6e3f64c343e189b38d/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/Utils.java
[modify] https://crrev.com/fda15c7a0c964e16dfed0c6e3f64c343e189b38d/chrome/android/java_sources.gni

Trace file per yfriedman's request

Deleted: uma.trace 368 KB

uma.trace 368 KB Download

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/dd04070aa5257204200985a97148f7f8de4d508b

commit dd04070aa5257204200985a97148f7f8de4d508b
Author: cco3 <cco3@chromium.org>
Date: Sat Apr 16 01:48:10 2016

Simplify Physical Web hook in Chromium startup

This will allow us to do more on startup without having to put more
lines into both the DeferredStartupHandler and the PhysicalWeb
class.  Eventually, we may want to record some UMA stats on startup,
and this will allow us to do so easily.

BUG= 594194 

Review URL: https://codereview.chromium.org/1882333002

Cr-Commit-Position: refs/heads/master@{#387785}

[modify] https://crrev.com/dd04070aa5257204200985a97148f7f8de4d508b/chrome/android/java/src/org/chromium/chrome/browser/DeferredStartupHandler.java
[modify] https://crrev.com/dd04070aa5257204200985a97148f7f8de4d508b/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/PhysicalWeb.java

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f4766630a78c1e35ef85211da0829f54d85541df

commit f4766630a78c1e35ef85211da0829f54d85541df
Author: cco3 <cco3@chromium.org>
Date: Mon Apr 18 20:30:43 2016

Record UMA for Physical Web state on debug actions

The "Physical Web state" refers to:
* Data connection
* BT permission/enablement
* Location permission/provider

We record this state:
* When launching the ListUrlsActivity from the diagnostics page
* When launching the ListUrlsActivity from the preferences page

BUG= 594194 

Review URL: https://codereview.chromium.org/1887523002

Cr-Commit-Position: refs/heads/master@{#388001}

[modify] https://crrev.com/f4766630a78c1e35ef85211da0829f54d85541df/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/PhysicalWebUma.java

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c8aece4cc68d2088887c01911f930292393bcddb

commit c8aece4cc68d2088887c01911f930292393bcddb
Author: cco3 <cco3@chromium.org>
Date: Wed May 25 22:27:15 2016

Record Physical Web status at Chrome startup

BUG= 594194 

Review-Url: https://codereview.chromium.org/2006363002
Cr-Commit-Position: refs/heads/master@{#396008}

[modify] https://crrev.com/c8aece4cc68d2088887c01911f930292393bcddb/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/PhysicalWeb.java
[modify] https://crrev.com/c8aece4cc68d2088887c01911f930292393bcddb/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/PhysicalWebUma.java