Bug 1553247 - Canonical list of known data anomalies

Data anomalies.txt

{
  "anomalies": [
    {
      "summary": "Armagaddon data deletion",
      "start_time": "2019-05-04T11:00:00Z",
      "end_time": "2019-05-11T11:00:00Z",
      "info_url": "https://bugzilla.mozilla.org/show_bug.cgi?id=1550787",
      "reference_urls": [
        "https://blog.mozilla.org/blog/2019/05/09/what-we-do-when-things-go-wrong/",
        "https://hacks.mozilla.org/2019/05/technical-details-on-the-recent-firefox-add-on-outage/",
        "https://docs.google.com/document/d/1q16Cn7uLX0Ir0ro5-oAQbylt0aBofGppwaTgKbA1qMc/edit#heading=h.12gb7xew9djd"
      ],
      "type": "outage",
      "scope": "All Firefox desktop telemetry data for the affected period",
      "detail": "During the Armag-Add-On situation, a hotfix was shipped as a Normandy study. In order to receive this hotfix, one needed to enable Telemetry uploads as well as enabling studies. This conflicts with the consent signal of opting in to Telemetry, and as such the decision was taken to delete Telemetry data collected during this period.",
      "affected_data": [ 
      	"main_summary",
      	"clients_daily",
        ...
      ]
    }, {
      ...
    }

  ]
}

summary: A brief, memorable name for the anomaly
type: an enum of known anomaly types. `measure change`, `event` (a-la Quantum launch, news cycle), `new measure`, etc
start_time: The earliest time data could be affected
end_time: The latest time data could be affected (if applicable - would be optional for some types)
info_url: The primary reference for this anomaly
reference_urls: Ancillary links to more information
scope: A description of which data was affected
detail: Expanded text about the anomaly
affected_data: We will want some way to determine which datasets are impacted, maybe at the column-level too