chore: notebook event logging to console

Author: Reita

src/events.ts

@@ -63,16 +63,6 @@ export interface NotebookEventData {
 export const send = (type: NotebookEventTypeValue, payload = '') => {
   const event: NotebookEventData = { type, payload };
   const parent = window.parent;
-
-  const { origin } = window.location;
-  const jupyterConfigData = JSON.parse(
-    document.getElementById('jupyter-config-data').textContent
-  );
-  fetch(
-    `${origin}${
-      jupyterConfigData.baseUrl
-    }api/contents?postMessage=${JSON.stringify(event)}`
-  );
   parent.postMessage(event, '*');
 };
 
@@ -206,6 +196,19 @@ export const onNotebookEventReceived = (
     NotebookUnmount
   } = NotebookEventType;
 
+  const { origin } = window.location;
+  const jupyterConfigData = JSON.parse(
+    document.getElementById('jupyter-config-data').textContent
+  );
+
+  /**
+   * We call jupyter's contents API; while this call technically does nothing it will log the API call to console which will be
+   * added to Cloudwatch where we will be able to query if needed.
+   */
+  fetch(
+    `${origin}${jupyterConfigData.baseUrl}api/contents?postMessage=${type}&origin=${message.origin}`
+  );
+
   switch (type) {
     /**
      * The idea for this event is that when the container is initializing the notebook, it can potentially send the state of a