Package: openedx-event-sink-clickhouse
PurposeThis project acts as a plugin to theEdx Platform, listens for
configuredOpen edX events, and sends them to aClickHousedatabase for
analytics or other processing. This is being maintained as part of theAspectsproject.OARS consumes the data sent to ClickHouse by this plugin as part of data
enrichment for reporting, or capturing data that otherwise does not fit in
xAPI.SinksCurrently the only sink is in the CMS. It listens for theCOURSE_PUBLISHEDsignal and serializes a subset of the published course blocks into one table
in ClickHouse.CommandsIn addition to being an event listener, this package provides commands for
exporting the same data in bulk. This allows bootstrapping a new data platform
or backfilling lost or missing data. Currently the only command is the Django
command for theCOURSE_PUBLISHEDdata:python manage.py cms dump_courses_to_clickhouseThis command allows bulk export of all courses, or various limiting factors.
Please see the command help for details:python manage.py cms dump_courses_to_clickhouse-hGetting StartedDevelopingOne Time Setup# Clone the repository
git clone git@github.com:openedx/openedx-event-sink-clickhouse.git
cd openedx-event-sink-clickhouse

# Set up a virtualenv using virtualenvwrapper with the same name as the repo and activate it
mkvirtualenv -p python3.8 openedx-event-sink-clickhouseEvery time you develop something in this repo# Activate the virtualenv
workon openedx-event-sink-clickhouse

# Grab the latest code
git checkout main
git pull

# Install/update the dev requirements
make requirements

# Run the tests and quality checks (to verify the status before you make any changes)
make validate

# Make a new branch for your changes
git checkout -b <your_github_username>/<short_description>

# Using your favorite editor, edit the code to make your change.
vim ...

# Run your new tests
pytest ./path/to/new/tests

# Run all the tests and quality checks
make validate

# Commit all your changes
git commit ...
git push

# Open a PR and ask for review.DeployingThe Open edX Event Sink Clickhouse component is a django plugin which doesn’t
need independent deployment. Therefore, its setup is reasonably
straightforward. First, it needs to be added to your service
requirements, and then it will be installed alongside requirements
of the service.This plugin will be deployed by default in an OARS Tutor environment. For other
deployments install the library or add it to private requirements of your
virtual environment (requirements/private.txt).Runpip installopenedx-event-sink-clickhouse.Run migrations:python manage.py lms migratepython manage.py cms migrateRestart LMS service and celery workers of edx-platform.ConfigurationCurrently all events will be listened to by default (there is only one). So
the only necessary configuration is a ClickHouse connection:EVENT_SINK_CLICKHOUSE_BACKEND_CONFIG = {
    # URL to a running ClickHouse server's HTTP interface. ex: https://foo.openedx.org:8443/ or
    # http://foo.openedx.org:8123/ . Note that we only support the ClickHouse HTTP interface
    # to avoid pulling in more dependencies to the platform than necessary.
    "url": "http://clickhouse:8123",
    "username": "changeme",
    "password": "changeme",
    "database": "event_sink",
    "timeout_secs": 3,
}Getting HelpDocumentationSeedocumentation on Read the Docs.More HelpIf you’re having trouble, we have discussion forums athttps://discuss.openedx.orgwhere you can connect with others in the
community.Our real-time conversations are on Slack. You can request aSlack
invitation, then join ourcommunity Slack workspace.For anything non-trivial, the best path is to open an issue in this
repository with as many details about the issue you are facing as you
can provide.https://github.com/openedx/openedx-event-sink-clickhouse/issuesFor more information about these options, see theGetting Helppage.LicenseThe code in this repository is licensed under the AGPL 3.0 unless
otherwise noted.Please seeLICENSE.txtfor details.ContributingContributions are very welcome.
Please readHow To Contributefor details.This project is currently accepting all types of contributions, bug fixes,
security fixes, maintenance work, or new features.  However, please make sure
to have a discussion about your new feature idea with the maintainers prior to
beginning development to maximize the chances of your change being accepted.
You can start a conversation by creating a new issue on this repo summarizing
your idea.The Open edX Code of ConductAll community members are expected to follow theOpen edX Code of Conduct.PeopleThe assigned maintainers for this component and other project details may be
found inBackstage. Backstage pulls this data from thecatalog-info.yamlfile in this repo.Reporting Security IssuesPlease do not report security issues in public. Please emailsecurity@openedx.org.