Closed Bug 1568838 Opened 7 years ago Closed 7 years ago

Smoke Test Glean crash count telemetry from Reference Browser integration

Categories

(Data Platform and Tools :: Glean: SDK, task, P2)

task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: travis_, Assigned: travis_)

References

Details

(Whiteboard: [telemetry:mobilesdk:m9])

With the &-browser instrumented with crash counts after Bug 1566169 landed, we should go back after we have had time for data to accumulate and make sure we are seeing what we expect to see.

According to Sebastian there are ways to make &-browser crash in order to inflate our numbers so we can get more data for testing:

about:crashcontent (non fatal content process crash, should show in-app snackbar for reporting)
and
about:crashparent (fatal crash should show dialog/notification)

Whiteboard: [telemetry:mobilesdk:m?] → [telemetry:mobilesdk:m9]
Assignee: nobody → tlong
Priority: P3 → P1
Summary: Analyze Glean crash count telemetry from Reference Browser integration → Smoke Test Glean crash count telemetry from Reference Browser integration

I just checked with Frank and we are still waiting on a schema change to land before we are actually ingesting crash data, but he says this should happen today.

I've prepared a query in order to smoke test this once the schema changes have landed and we've had a couple of days to collect some crashes (including some I plan on generating myself).

Pushing this to P2 and planning on taking it back up next week.

Priority: P1 → P2

Nevermind, looks like Frank came to the rescue and provided this: https://sql.telemetry.mozilla.org/queries/64067/source

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.