Skip to content
This repository has been archived by the owner on Nov 21, 2023. It is now read-only.

Have python_moztelemetry use the Probe Info Service instead of mozilla-central parsers #193

Open
chutten opened this issue Feb 5, 2018 · 1 comment

Comments

@chutten
Copy link
Contributor

chutten commented Feb 5, 2018

Nobody likes server-side parsing. So we should let the Probe Info Service do it for us. Then we can delete all the vendored parsers!

@chutten
Copy link
Contributor Author

chutten commented Aug 28, 2018

@fbertsch, @robhudson, and I had a conversation about this today.

There were a couple of details that cropped up that make this interesting:

  1. mozaggregator seems to be the only service that cares about parsing custom (ie, not tip of tree) definitions files. And it only does so in order to show probes in Beta that have been removed in Nightly, until that removal of the probe reaches Beta.
  2. Adopting the Probe Info Service means no longer being sure whether a probe coming from a client was expired in that client's build (since probeinfo has revs which aren't comparable without a VCS setup). Maybe if we had buildids in the probeinfo we could compare.
  3. We're not too concerned about the perf and size implications of aggregating the extra data coming in from older builds on channels whose definitions files have had probes removed. Probe owners are already bad for leaving expired probe definitions in place in perpetuity already.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant