Files
edx-platform/common/djangoapps/track
Tim McCormack e0e03dec5f Use more appropriate hash when making tracking ID; document SECRET_KEY use (#26134)
- Make it easier to rotate `SECRET_KEY` by documenting this usage
  for both sensitivity and rotation process. (ARCHBOM-1676).
- Just use a hash of the secret rather than HMAC + MD5. We're not
  authenticating a message, so HMAC isn't really needed -- it just needs
  to be unique, deterministic, and irreversible. SHAKE allows generation
  of an arbitrary length hash without needing to truncate.

Also, rename tracking session ID generator for clarity -- there's no
encryption happening here.

Add additional test for existing claim of uniqueness.
2021-01-27 14:13:42 +00:00
..
2019-12-30 10:35:30 -05:00
2019-04-25 13:53:55 -04:00
2019-12-30 12:25:38 -05:00
2019-12-30 12:25:38 -05:00
2019-12-30 12:25:38 -05:00

Status: Maintenance

Responsibilities
================
The Track app records student tracking events into logs for later analysis by Insights and academic research teams. It provides an endpoint for front end code to asynchronously send user tracking events, as well as providing middleware to record server calls.

While new event types are being added all the time, the Track app for recording those events is not under active development.

Glossary
========


More Documentation
==================
`Events in the Tracking Logs <https://edx.readthedocs.io/projects/devdata/en/stable/internal_data_formats/tracking_logs.html>`_