Bug 1647825 - Add a schema for the new ping 'xfocsp-error=report'. #570
Conversation
acmiyaguchi
left a comment
acmiyaguchi
left a comment
There was a problem hiding this comment.
Based on the data review in the bug, this data collection contains category 4 data and is therefore blocked on bug 1651005. /cc @whd for visibility.
|
@acmiyaguchi Could you trigger the integration CI test for this? And does this PR need to wait until bug 1651005 been resolved? Thanks. |
|
Running the integration tests now. And yes, in general we have only collected category 1 and 2 data in Telemetry. While there are crash pings, the more sensitive crash reports are submitted into a separate Socorro pipeline. I am not comfortable making category 4 data available in the system until we have strict access controls in place. Merging this PR will deploy the schema to the ingestion system and BigQuery, which allow all moco access to any submitted data. cc @mreid-moz |
Closes #570 This pulls in the commit from that PR and duplicates it in a new namespace. We will be rerouting these pings in the pipeline so that they can have stricter access controls. There is a test case added here so that CI will fail if these two schemas get out of sync.
* Bug 1647825 - Add a schema for the new ping 'xfocsp-error=report'. * Bug 1654558 Add xfocsp-error-report schema Closes #570 This pulls in the commit from that PR and duplicates it in a new namespace. We will be rerouting these pings in the pipeline so that they can have stricter access controls. There is a test case added here so that CI will fail if these two schemas get out of sync. Co-authored-by: Tim Huang <tihuang@mozilla.com>
3 participants
Checklist for reviewer:
.circleci/config.yml) will cause environment variables (particularly credentials) to be exposed in test logsintegrationCI test by pushing this revision as discussed in the README and review the report posted in the comments.For glean changes:
include/glean/CHANGELOG.md