Closed
Bug 1659750
Opened 5 years ago
Closed 5 years ago
Add telemetry/account-ecosystem to mozilla-schema-generator
Categories
(Data Platform and Tools :: General, enhancement, P2)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: klukas, Assigned: klukas)
References
Details
Attachments
(2 files)
As discussed in https://bugzilla.mozilla.org/show_bug.cgi?id=1635659#c43, it looks like the right thing to do for the telemetry/account-ecosystem
ping is to handle it like main pings, where we have the schema generator add probe-specific fields.
I have not done any substantial work with m-g-s, so want to get advice about how to proceed. This is my understanding of the rough shape of the change:
- Add placeholders in the account-ecosystem schema for payload.processes.X.scalars, etc.
- add account-ecosystem to configuration of m-g-s and tell it to add all probes sent to the
account-ecosystem
metrics store
?ni anthony, frank: Should the above be fairly straight-forward? Is there complexity I'm missing?
Assignee | ||
Updated•5 years ago
|
Blocks: aet-pipeline
Assignee | ||
Updated•5 years ago
|
Flags: needinfo?(fbertsch)
Flags: needinfo?(amiyaguchi)
Comment 1•5 years ago
|
||
Comment 2•5 years ago
|
||
Updated•5 years ago
|
Flags: needinfo?(amiyaguchi)
Assignee | ||
Comment 3•5 years ago
|
||
Frank gave me the advice I needed yesterday. I now have PRs staged and tagged Frank for review.
Flags: needinfo?(fbertsch)
Assignee | ||
Comment 4•5 years ago
|
||
Support is now merged and deployed to stage. The nonprod version of the table includes the probes. The new schema should be deployed to prod within 24 hours.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•