Missing events COURSE_CREATED and TRACKING_EVENT_EMITTED

Development
, ,
1

I have been trying to use the tracking_event_emitted event and also the course_created event from the openedx_events. For context, I am using the redwood.master with tutor dev. Is there any flag or feature setting that I should set in order for the event to get emitted similar to the certificate event? I can see the course_created emitting code in here (edx-platform/xmodule/modulestore/mixed.py at fe80a1cdcd285bddc48eec5313ef819963f26b52 · openedx/edx-platform · GitHub), but there is no clue of the tracking_event_emitted event.
Any help would be appreciated!

2

Hi there,

I don’t believe we have a tracking event for course creation right now. There is the openedx-event, which you referenced above, but those do not automatically create a tracking log event. The list of tracking events is here: Alphabetical Tracking Log Event List — Latest documentation

If you are writing custom plugins for edx-platform already it wouldn’t be too hard to add a listener to the COURSE_CREATED event and create your own tracking log statement from there.

3

Thanks for the reply!
This was the tracking event I was talking about..
I was trying to add listener for both the COURSE_CREATED and the TRACKING_EVENT_EMITTED events. As you mentioned, I don’t think TRACKING_EVENT_EMITTED is yet implemented, but for the COURSE_CREATED event, it is not get emitted it seems as the listener function I created is not working.
I have a similar setup for the STUDENT_REGISTRATION_COMPLETED event and it is working fine!

4

Ah, I see! That makes sense. TRACKING_EVENT_EMITTED is implemented, but requires some configuration for event_tracking to send those events. Are you planning on using the event bus for these events, or just listening for using an in-process signal handler?

Probably a silly thing to check, but COURSE_CREATED should generally only get fired in Studio, so make sure you’re looking in the right logs for those.

5

I was just planning to listen to the events and nothing else.
I too might have made a silly mistake. I had not added entry point to CMS on my django plugin, I’ll try if that is the issue.

6

@BrianMesick thanks for that heads up you had given! The issue was that I didn’t add the entry point to the CMS. It worked after I added the CMS entry point!

1 Like