Bugzilla

Bug #1626698 covers building a schema for crash annotations which internally we call the "raw crash". That would help with sorting out problems with incoming crash data and help people writing crash reporters debug their code.

Bug #1753521 covered fixing Elasticsearch indexing to only index data from the processed crash. This simplifies indexing because the processed crash contains data that has been normalized and validated.

Bug #1755095 covered fixing Telemetry crashstorage to build a crash document solely from the processed crash. The processed crash data has been normalized and validated and it reduced the complexity of the Telemetry crashstorage code.

Bug #1755525 covers changing the webapp report view to only show data from the processed crash. Since the processed crash data is normalized and validated, this will simplify the report view code.

Once all that work is done, we'll be depending on the processed crash. If we make a schema for that data, we can additionally centralize all the data access permissions and the webapp view code.

This bug covers creating a processed crash schema that specifies structure and types for data as well as permissions that'll be used by the API, report view, and (later) super search fields.

Bug #1753521 covered fixing Elasticsearch indexing to only index data from the processed crash. This simplifies indexing because the processed crash contains data that has been normalized and validated.

Bug #1755095 covered fixing Telemetry crashstorage to build a crash document solely from the processed crash. The processed crash data has been normalized and validated and it reduced the complexity of the Telemetry crashstorage code.

Bug #1762271 covered replacing the json schema reducer so that we can use schemas to encode metadata for other purposes and transforms.

All that work leads us to a point where we can build a processed crash schema.

The processed crash schema will let us centralize a few things:

1. a better way to denote which fields to copy/normalize/validate from the raw crash for the `CopyFromRawCrashRule`
2. access control for processed crash fields simplifying a bunch of access-control-like thing littered across the code base
3. documentation for the fields including descriptions
4. indexing and search instructions (this requires a lot more work to our Elasticsearch code)

This bug covers creating a processed crash schema that specifies structure and types for data as well as permissions that'll be used by the API, report view, and (hopefully) super search fields.