Closed Bug 1757451 Opened 3 years ago Closed 3 years ago

attribution.dltoken missing from messaging-system/onboarding schema

Categories

(Data Platform and Tools :: General, task)

task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: klukas, Unassigned)

References

Details

(Whiteboard: [dataquality])

We noticed in weekly pipeline health triage that the messaging-system/onboarding ping sometimes contain an attribution.dltoken field that is not present in the schema. Should it be added to the schema? Are we expecting to see this field populated?

?ni :nanj

Flags: needinfo?(najiang)
Whiteboard: [data-quality]

We noticed in weekly pipeline health triage that the messaging-system/onboarding ping sometimes contain an attribution.dltoken field that is not present in the schema. Should it be added to the schema? Are we expecting to see this field populated?

I am not sure about if this is a new addition to the schema.

Bouncing NI to :pdahiya.

Flags: needinfo?(najiang) → needinfo?(pdahiya)
Depends on: 1677497

After chatting with Punam in another thread, confirmed the attribution.dltoken was added and data reviewed in bug 1677497.

She will make a PR to add this field to the schema.

(In reply to Punam Dahiya [:pdahiya] from comment #2)

NI @kirk to help confirm that dlToken attribution is reliable and now collected for all channels and not just Nightly.

As far as I know, it has been collected for all channels since it was added in Bug 1677497. I'm not sure what to say about how reliable it is. I'm not particularly familiar with the code that creates and retrieves this data. I just added the plumbing so that we would store the value and add it to the telemetry.

Flags: needinfo?(bytesized)

Thanks for submitting the patch! This is now merged, and the field will be added to the relevant tables with the next schema deploy within 24 hours.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Component: Pipeline Ingestion → General
Whiteboard: [data-quality] → [dataquality]
You need to log in before you can comment on or make changes to this bug.