1273688 - Validate core ping fields - search counts & session usage

Status: RESOLVED WONTFIX

(Data Platform and Tools :: General, defect, P2)

Description

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Consider batching with bug 1268513 and/or bug 1271391.

Comment 1

[Georg Fritzsche [:gfritzsche]]

Moving this so it shows up in the data platform triaging for planning & consideration.

Comment 2

[Thomas Huelbert]

Hey Frank, is this still needed?

Comment 3

[Frank Bertsch [:frank]]

I'm not sure - this predates me. Georg, any idea what kind of validation this was? Just general numbers look okay, or sending specific ping from a client and validating it is correct on our end, etc.?

Comment 4

[Georg Fritzsche [:gfritzsche]]

We were looking for the following for client changes:
- type validation for the new fields
- mapping out numbers whether they look sensible
  - overall totals
  - per ping count distribution should make sense
  - per client and day distribution should make sense
- here specifically: sanity look at search engine count distribution, does that look "sane" to PMs or so

Comment 5

[Georg Fritzsche [:gfritzsche]]

Some prior art:
https://gist.github.com/georgf/56449b46623ce2493b01a82d0dd08e6e

Note that for search counts specifically, we may have legal/contract issues with publishing them outside of MoCo.

Comment 6

[Rob Miller [:rmiller]]

Hello,

The Mozilla Data Engineering organization is currently going through our extensive backlog, consisting of hundreds of issues stretching back for nearly 10 years. We've done a pass through all of the open bugzilla bugs and have identified and tagged the ones that we think are relevant enough to still need attention. The rest, including the bug with which this comment is associated, we are closing as "WONTFIX" in a single bulk operation.

If you feel we have closed this (or any) issue in error, please feel free to take the following actions:

• Reopen the bug.
• Edit the bug to add the string [dataplatform] (including the brackets) to the Whiteboard field. (Note that you must edit the Whiteboard, not the similarly named QA Whiteboard.)

Doing this will ensure that we see the bug in our weekly triage process, where we will decide how to proceed.

Thank you.