-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Telemetry] Error Pages #1242
Comments
@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. |
@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? |
Should be fixed by #3224. |
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/ 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. |
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 |
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:
Please find attached the logcat Error.txt @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 |
Description & Product Manager User Story
What questions will you answer with this data?
Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?
What probes (suggested, if applicable)
Dependencies (Added by PM and Eng)
Acceptance Criteria (Added by PM)
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: