We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The telemetry ID is being deprecated in favor of a sha256 hashed ID.
Rename variables from client_id toclient_hash in taar for clarity.
client_id
client_hash
Update all ETL jobs in python_mozetl related to TAAR to compute and use hashes instead of raw telemetry client ID.
The text was updated successfully, but these errors were encountered:
Coordinate with @ddurst regarding the particular HTTP header naming and encoding of the sha hash
Sorry, something went wrong.
This code has landed in python_mozetl as of mozilla/python_mozetl#267
The relevant patch on the TAAR application code to convert from a UUID to a hashed telemetry ID is included in #128
See line:
taar/taar/plugin.py
Line 38 in e4efb74
Hashed client ID landed in f279c25.
Tests were updated in 32a3e64
No branches or pull requests
The telemetry ID is being deprecated in favor of a sha256 hashed ID.
Rename variables from
client_id
toclient_hash
in taar for clarity.Update all ETL jobs in python_mozetl related to TAAR to compute and use hashes instead of raw telemetry client ID.
The text was updated successfully, but these errors were encountered: