Firefox Core Engineering/Get More Data Faster: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Marked the pingsender task as completed)
(updated, 2017-03-27)
Line 1: Line 1:
This effort is establish a shorter path between client crashes and actionable data.
This effort is establish a shorter path between client crashes and actionable data.


== Step 1==
==Step 1==
# <strike>Land content crash ping (enables new crash ping types)​.​ [end of Q4 2016]</strike> completed: {{Bugzilla|1293656}}
# <strike>Land content crash ping (enables new crash ping types)​.​ [end of Q4 2016]</strike> completed: {{Bugzilla|1293656}}
# Determine how to report on unsymbolicated stack in crash pings (we want to identify what we can answer from the data we collect now, without aggregating and without symbolicating)​.​ [mid-January 2017]
# <strike>Determine how to report on unsymbolicated stack in crash pings (we want to identify what we can answer from the data we collect now, without aggregating and without symbolicating)​.​ [mid-January 2017]</strike>
# Scale/load test the new symbolapi.m.o (we want to know if this will serve its current function AND a future function for release users)​. [mid-January 2017]
# <strike>Scale/load test the new symbolapi.m.o (we want to know if this will serve its current function AND a future function for release users)​. [mid-January 2017]</strike> This has been abandoned in favor of a rewrite led by peterbe.
# <strike>Determine if we can include frame pointers on release (because it enables future steps). [end of Q4 2016]​</strike> completed: {{Bugzilla|1322735}}
# <strike>Determine if we can include frame pointers on release (because it enables future steps). [end of Q4 2016]​</strike> completed: {{Bugzilla|1322735}}


== Step 2==
==Step 2==
# <strike>Land the pingSender (so we can send a crash ping as soon as possible)​. [mid-January 2017]</strike> completed​: {{Bugzilla|1310703}}
# <strike>Land the pingSender (so we can send a crash ping as soon as possible)​. [mid-January 2017]</strike> completed​: {{Bugzilla|1310703}}
# Symbolicate crash ping stacks either via batch in data processing or client-side -- depending on the outcome of Step 1.3 and 1.4.​ [TBD]​
# Symbolicate crash ping stacks via batch in data processing.​ [TBD]​
# Create "client-side" signatures from symbolicated stacks via batch in data processing.​ [TBD]​


==Step 3==
==Step 3==
# Create "client-side" signatures -- depending on Step 2.2 (whether the stacks in crash pings are symbolicated or not) and Step 1.2 (whether we need to establish these signatures in a data source or in a process on the ping itself).​ [TBD]​
# Implement clustering of crashes on the client-side, based on signatures. [TBD]
# Possibly introduce new crash ping types (gpu, etc).​ [TBD]​
# Establish means of identifying top crashers in client-side data. [TBD]
# Allow for correlating between client-side crash clusters and crash-stats-side crash clusters. [TBD]


==Step 4==
==Step 4==
# Implement clustering of crashes on the client-side (probably based on signatures) -- depending on Step 3.1. [TBD]
# Symbolicate crash ping stacks on the client, via https://symbolserver.mozilla.org/symbolicate (see peterbe). [TBD]
# Return signatures to the client, via a signature service. [TBD]


==Step 5==
==Step 5==
# Allow for correlating between client-side crash clusters and crash-stats-side crash clusters. [TBD]
# Introduce new crash ping types beyond Main and Content (gpu, webextension, etc).​ [TBD]​

Revision as of 01:19, 28 March 2017

This effort is establish a shorter path between client crashes and actionable data.

Step 1

  1. Land content crash ping (enables new crash ping types)​.​ [end of Q4 2016] completed: 1293656
  2. Determine how to report on unsymbolicated stack in crash pings (we want to identify what we can answer from the data we collect now, without aggregating and without symbolicating)​.​ [mid-January 2017]
  3. Scale/load test the new symbolapi.m.o (we want to know if this will serve its current function AND a future function for release users)​. [mid-January 2017] This has been abandoned in favor of a rewrite led by peterbe.
  4. Determine if we can include frame pointers on release (because it enables future steps). [end of Q4 2016]​ completed: 1322735

Step 2

  1. Land the pingSender (so we can send a crash ping as soon as possible)​. [mid-January 2017] completed​: 1310703
  2. Symbolicate crash ping stacks via batch in data processing.​ [TBD]​
  3. Create "client-side" signatures from symbolicated stacks via batch in data processing.​ [TBD]​

Step 3

  1. Implement clustering of crashes on the client-side, based on signatures. [TBD]
  2. Establish means of identifying top crashers in client-side data. [TBD]
  3. Allow for correlating between client-side crash clusters and crash-stats-side crash clusters. [TBD]

Step 4

  1. Symbolicate crash ping stacks on the client, via https://symbolserver.mozilla.org/symbolicate (see peterbe). [TBD]
  2. Return signatures to the client, via a signature service. [TBD]

Step 5

  1. Introduce new crash ping types beyond Main and Content (gpu, webextension, etc).​ [TBD]​
Retrieved from "https://wiki.allizom.org/index.php?title=Firefox_Core_Engineering/Get_More_Data_Faster&oldid=1166802"