OOMAllocationSize missing from BigQuery crash_v4 table schema
Categories
(Data Platform and Tools :: General, defect)
Tracking
(Not tracked)
People
(Reporter: tdsmith, Assigned: amiyaguchi)
References
Details
Attachments
(1 file)
(deleted),
text/x-github-pull-request
|
Details |
crash_summary
had a payload.metadata.OOMAllocationSize
key. There's no equivalent in the BigQuery crash_v4
table, though it is present in additional_properties
. It's only present if a crash was a OOM crash.
Comment 1•5 years ago
|
||
It does indeed seem to be missing from the schema:
May be worth doing a quick pass to see if there are any other fields in the payload which could be trivially added.
Assignee | ||
Comment 2•5 years ago
|
||
There are quite a few fields missing, in particular in the payload.metadata
struct. There's a view for enumerating paths in the additional_properties field in the ping tables under moz-fx-data-shared-prod.monitoring.telemetry_missing_columns_v1
. Check this redash query for a list of affected fields, including OOMAllocationSize.
Comment 3•5 years ago
|
||
FYI the fields of a crash ping are extensively documented here:
https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/data/crash-ping.html
Additionally all the subfields of payload.metadata
can be extracted from CrashAnnotations.yaml
. They are the entries flagged with ping: true
.
Assignee | ||
Comment 4•5 years ago
|
||
Reporter | ||
Comment 5•5 years ago
|
||
I think your pull request fixed this, right? (Thanks!)
Assignee | ||
Comment 6•5 years ago
|
||
It did, the field should be available as of 2019-11-14 (https://sql.telemetry.mozilla.org/queries/66646/source).
Updated•5 years ago
|
Updated•2 years ago
|
Description
•