-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add per-client measurements and additional queries for v4 experiment #41
Comments
k88hudson
added a commit
to k88hudson/mozilla-pipeline-schemas
that referenced
this issue
Nov 24, 2022
k88hudson
added a commit
to k88hudson/mozilla-pipeline-schemas
that referenced
this issue
Nov 24, 2022
k88hudson
added a commit
to k88hudson/mozilla-pipeline-schemas
that referenced
this issue
Nov 24, 2022
akkomar
pushed a commit
to mozilla-services/mozilla-pipeline-schemas
that referenced
this issue
Nov 25, 2022
k88hudson
added a commit
to k88hudson/mozilla-pipeline-schemas
that referenced
this issue
Dec 1, 2022
5 tasks
fbertsch
pushed a commit
to mozilla-services/mozilla-pipeline-schemas
that referenced
this issue
Dec 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to support additional analysis that correlates data on our end with queries on the NS side, we'd like to add an additional set of queries for per-client domains, as well as some record types we weren't previously checking (specifically
DS
andA
with the NOEDNS flag set).This will involve some changes to our tables in the data pipeline for the new keys. Additionally, we'd like to send errors that resulted as part of attempting to send a query as part of the final payload instead of separately.
Experimenter link: https://experimenter.services.mozilla.com/experiments/dnssec-interference-measurement-with-per-client-measurements-v4/
The text was updated successfully, but these errors were encountered: