Bug 1553455 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Brief description of the request:
Telemetry was shipped to help better understand the impact that specific modules have on user experience and we want to make this telemetry accessible to most people at Mozilla to help understand / troubleshoot DLL issues and make decisions on blocklist additions.

Dashboard requirements:
- Provide a stack that relates to a DLL name
- All untrusted modules, sorted by load time
- All untrusted modules, sorted by crash frequency
- Floor frame: Given a particular floor frame, what is the frequency of its use as an injection mechanism?
- Top DLLs that correlate with engagement metrics drop (search count, session time, URIs browsed ...)
- Top DLLs that correlate with retention drop (3 week retention?)

Link to any assets:
Previous work done: https://docs.google.com/document/d/1r8PSHrEFeVc7S7kzrDnRq28_MRUreP9_cePyKDj8i8A/edit

Is there a specific data scientist you would like or someone who has helped to triage this request:
No
Revision 1 by
on 
Brief description of the request:
Telemetry was shipped to help better understand the impact that specific modules have on user experience and we want to make this telemetry accessible to most people at Mozilla to help understand / troubleshoot DLL issues and make decisions on blocklist additions.

Dashboard requirements:
- Provide a stack that relates to a DLL name
- All untrusted modules, sorted by load time
- All untrusted modules, sorted by crash frequency
- Floor frame: Given a particular floor frame, what is the frequency of its use as an injection mechanism?
- Top DLLs that correlate with engagement metrics drop (search count, session time, URIs browsed ...)
- Top DLLs that correlate with retention drop (3 week retention?)
- Top DLLs by share of users impacted
- Top DLLs causing the bootstrap process to crash

Link to any assets:
Previous work done: https://docs.google.com/document/d/1r8PSHrEFeVc7S7kzrDnRq28_MRUreP9_cePyKDj8i8A/edit

Is there a specific data scientist you would like or someone who has helped to triage this request:
No
Revision 2 by
on 
Brief description of the request:
Telemetry was shipped to help better understand the impact that specific modules have on user experience and we want to make this telemetry accessible to most people at Mozilla to help understand / troubleshoot DLL issues and make decisions on blocklist additions.

Dashboard requirements:
- Provide a stack that relates to a DLL name
- All untrusted modules, sorted by load time with a filter on "share of users impacted above X"
- All untrusted modules, sorted by crash frequency with a filter on "share of users impacted above X"
- All untrusted modules sorted by share of users impacted
- All untrusted modules causing the bootstrap process to crash sorted by frequency of occurence
- Floor frame: Given a particular floor frame, what is the frequency of its use as an injection mechanism?
- Top DLLs that correlate with engagement metrics drop (search count, session time, URIs browsed ...) with a filter on "share of users impacted above X"
- Top DLLs that correlate with retention drop (3 week retention?) with a filter on "share of users impacted above X"

Link to any assets:
Previous work done: https://docs.google.com/document/d/1r8PSHrEFeVc7S7kzrDnRq28_MRUreP9_cePyKDj8i8A/edit

Is there a specific data scientist you would like or someone who has helped to triage this request:
No

Back to Bug 1553455 Comment 0