[Telemetry] Error Pages

[bbinto]

Description & Product Manager User Story

• As a product owner, I want to know when people encounter errors on websites so we know when they

What questions will you answer with this data?

• When and what errors users experience within the app
• What will users do after they've encountered an error (Amplitude funnel) and how will they get out of it

Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?

• Understand the health of the web and how often users encounter website errors

What probes (suggested, if applicable)

• send an event ping on each specific error, see here for kind of errors

Dependencies (Added by PM and Eng)

• Glean SDK

Acceptance Criteria (Added by PM)

• Event pings can be queried via re:dash
• We are sending telemetry events for the actions listed in the requirements
• We have documented the telemetry
• We have asked a data steward to review the telemetry
• NOT an AC: Data science to create dashboard or further graphs (this will be a separate issue, this issue is only about hooking up the events described and that they can be queried in re-dash)

┆Issue is synchronized with this Jira Task

[sblatz]

@vesta0 is there any other data we want to track in this? I'm understanding this ticket to mean that we're just going to send a ping with the error type (e.g. ERROR_NET_TIMEOUT) and no other information.

[vesta0]

@sblatz I think that's about it (when and what error type). We also want to track what users do right after they've encountered the error but I think that depends on other probes we have put in place, would you agree?

[sblatz]

Should be fixed by #3224.

[AndiAJ]

Hi, the error_page still doesn't work.

Please find attached and review the logcat Errortxt.txt and the log from the dashboard (https://debug-ping-preview.firebaseapp.com/pings/2311bde3-47fc-4272-9a8b-b1cce4e7eaf5/aj-TezzErr-00)

I've used the following websites to trigger the errors:

https://www.fakeurlwebsite.org/
http://mediarepoes.net/
http://www.odiadon.com/
http://tessline.com/
https://testsafebrowsing.appspot.com/s/phishing.html
https://testsafebrowsing.appspot.com/s/unwanted.html
https://expired.badssl.com

One question though, @sblatz shouldn't it be correlated with "searched_page" event ping? After accessing a page only afterwards the error should pop up ?

Based on this comment I'll remove the QA needed label.

[sblatz]

Could @boek weigh in here? I'm really not sure what else would be the issue here. I'm able to get the telemetry line triggered in my debugging. I wonder if the AppRequestInterceptor is for some reason not compatible with Telemetry?

[AndiAJ]

Hi, verified as fixed on the latest Fenix version (2019-06-14) using a Google Pixel 3XL(Android 9)

I've used the following websites to trigger the errors:

https://www.fakeurlwebsite.org/
http://mediarepoes.net/
http://www.odiadon.com/
http://tessline.com/
https://testsafebrowsing.appspot.com/s/phishing.html
https://testsafebrowsing.appspot.com/s/malware.html
https://testsafebrowsing.appspot.com/s/unwanted.html
https://expired.badssl.com

Please find attached the logcat Error.txt
and the link from the dashboard:https://debug-ping-preview.firebaseapp.com/pings/c9dd95fc-79ff-455b-ac97-eac9d4ccc7df/aj-testerr-140600

@boek @sblatz - Please review the attached logs and if any problems encountered, reopen this ticket.

Based on this comment I'll remove the QA needed label and close the ticket