total_uri_count should be added to the metrics ping

[boek]

┆Issue is synchronized with this Jira Task

[AndiAJ]

Hi, I've just checked on the latest Nightly Build #13040608 from 31/10 using a Google Pixel 3a XL (Android 9) and noticed the following:

• Performed 3 searches
The baseline ping 294b7f7a-c381-483f-b7b8-9cdcc0a3a1c0 shows "events.total_uri_count": 4
The metrics ping shows bb9612e8-a4c9-4e85-9cee-caebc871798a shows "metrics.total_uri_count": "0"
Logcat
Glean dashboard

• Performed 6 searches
The baseline 6b6cf012-661e-4fd3-b505-452b8565a0cc ping shows "events.total_uri_count": 7
The metrics ping shows 5f94bcc1-9239-4ed9-bb99-57c3750d1330 shows "metrics.total_uri_count": "0"
Logcat
Glean Dashboard

@sblatz please help me out with the following:
Why is the total_uri_count = to the numer of searches + 1? in both cases
Why the "metrics.total_uri_count" isn't displayed in the logs from Android Studio?

To generate the metrics ping I've force stopped Fenix, set the date to T+1 (01/11) and set the time to 03:59AM. At around 4AM the metrics ping is generated and sent.
Based on the "client_id" & the "first_run_date" in both cases the metrics is properly generated.

Please review the above. 😊
I'll remove the QA needed label until further clarifications.

[sblatz]

Why is the total_uri_count = to the numer of searches + 1? in both cases

I think @baron-severin may be able to answer this better?

Why the "metrics.total_uri_count" isn't displayed in the logs from Android Studio?

Investigating this one.

[severinrudie]

Why is the total_uri_count = to the numer of searches + 1? in both cases

I think @baron-severin may be able to answer this better?

I don't actually have any context on this one. I noticed a related bug, but don't know anything else about this ping.

[sblatz]

@boek maybe? I think he was the one who added this :)

[sblatz]

I have addressed "metrics.total_uri_count": being 0 and marking this ready for qa needed again.

I'm not sure why the total_uri_count is one plus the search number, though. We can address that in another ticket?

[AndiAJ]

Hi, I've just re-tested on Nightly Build #13160607 from 12/11 using a Google Pixel 3a XL (Android 9) phone and learned the following:

Performed 3 searches and generated the metrics ping:
"metrics.total_uri_count": "4"

Performed 6 searches and generated the metrics ping:
"metrics.total_uri_count": "7"

Logcat
Glean dashboard

@sblatz I think we should first try to solve the mystery behind #6499 from the baseline pings and afterwards re-test this matter.
Please share your thoughts on this. ☺️

@Dexterp37 - While testing this matter I've noticed that "metrics.total_uri_count": is displayed only when checking the metrics pings in the Glean dashboard and not in the logcat from Android Studio.
Do you know why is this happening? ☺️

I'll remove the QA needed label until further clarifications.

[Dexterp37]

@Dexterp37 - While testing this matter I've noticed that "metrics.total_uri_count": is displayed only when checking the metrics pings in the Glean dashboard and not in the logcat from Android Studio.
Do you know why is this happening? ☺️

@AndiAJ what is the id of the specific ping that shows up on the dashboard but not in the logs? I randomly picked 52c2e975-6998-4ac2-bc94-46fcf189d0c0 from the debug view and it shows up in the logs.

Update After talking to @AndiAJ , we found that Android logcat is limiting the length of log messages and thus cropping local ping contents in the logs. I filed this bug. QA can still be performed using the glean ping view.

[sblatz]

@AndiAJ can you tell me what steps you're performing to do these searches? I've tested locally and I seem to be getting the right number of total_uri_count (3 searches = 3 for total_uri_count).

[liuche]

Just a bump here @AndiAJ ^

[sblatz]

@liuche We're going to need to fix this bug mentioned by Glean team: #6577. We should pull that into a sprint if we want to get this ticket closed.

[boek]

Going to track in #6577