You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to use the transform_tracking_logs command to bulk-load historical data into our edX Aspects environment, with Ralph as the LRS.
We would like the ability to specify a particular LRS to send the data to (e.g., using a flag such as --LRS) so that the data is sent exclusively to Ralph.
Currently, the command does not support this functionality, which means all tracking logs are sent to all configured LRSs. This is a problem for us, as we do not want to spam the existing LRSs with tracking logs spanning several years.
The text was updated successfully, but these errors were encountered:
Introduced the --lrs-urls argument to allow specifying multiple LRS route URLs.
This enhancement enables sending tracking logs exclusively to the designated LRSs,
preventing data from being sent to all configured LRSs.
closeopenedx#483
- Introduced the --lrs-urls flag to specify target Learning Record Stores (LRS) by their route_url.
- Updated documentation to reflect the new usage of the --lrs-urls option.
- Added tests to ensure correct functionality when using the --lrs-urls flag.
closeopenedx#483
Ali-Salman29
added a commit
to Ali-Salman29/event-routing-backends
that referenced
this issue
Feb 6, 2025
- Introduced the --lrs-urls flag to specify target Learning Record Stores (LRS) by their route_url.
- Updated documentation to reflect the new usage of the --lrs-urls option.
- Added tests to ensure correct functionality when using the --lrs-urls flag.
closeopenedx#483
We are trying to use the transform_tracking_logs command to bulk-load historical data into our edX Aspects environment, with Ralph as the LRS.
We would like the ability to specify a particular LRS to send the data to (e.g., using a flag such as --LRS) so that the data is sent exclusively to Ralph.
Currently, the command does not support this functionality, which means all tracking logs are sent to all configured LRSs. This is a problem for us, as we do not want to spam the existing LRSs with tracking logs spanning several years.
The text was updated successfully, but these errors were encountered: