1875874 - schema error in `telemetry.bhr_v4`, `telemetry.main_v4`, and other pings for #/environment/system/os/distro

Status: RESOLVED FIXED

(Data Platform and Tools :: General, defect)

Description

[Anna Scholtz [:ascholtz]]

A new schema error is happening for bhr pings for #/environment/system/os/distro: expected type: String, found: Null
Currently around 14k

Comment 1

[Sean Rose [:srose]]

I'm expanding this bug's scope, since the same schema error is now also happening for six additional legacy telemetry pings:

• crash_v4
• event_v4
• first_shutdown_v4
• main_v4
• modules_v4
• new_profile_v4

Hopefully this is just a case of the browser implementation/rollout lagging behind telemetry schema definitions, and these will taper off.

Comment 2

[BMO Github Automation]

Attachment: [mozilla-services/mozilla-pipeline-schemas] Bug 1875874 - Allow null distro and distroVersion in telemetry (#810)

Comment 3

[Ben Wu [:benwu]]

The errors stopped when dataflow redeployed at around 2024-05-01 19:00:00 UTC

SELECT
  document_type,
  DATE_TRUNC(submission_timestamp, HOUR),
  COUNT(*),
FROM
  `moz-fx-data-shared-prod.payload_bytes_error.telemetry`
WHERE
  DATE(submission_timestamp) BETWEEN '2024-05-01' AND '2024-05-02'
  AND (
    error_message = 'org.everit.json.schema.ValidationException: #/payload/os/distro: expected type: String, found: Null'
    OR error_message = 'org.everit.json.schema.ValidationException: #/environment/system/os/distro: expected type: String, found: Null'
  )
GROUP BY document_type, 2
ORDER BY 2, document_type

Related fix in firefox is bug 1894412