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
Our telemetry project, ETC JupyterLab Telemetry Extension, captures user interactions and logs these messages to a specified handler. The ETC JupyterLab Telemetry Example repo gives an example of the service provided by the extension being consumed and the events being logged to console.log.
Presently, we are capturing several user interactions with the Notebook:
Active Cell Changed
Cell Added
Cell Executed
Cell Removed
Notebook Opened
Notebook Saved
Notebook Scrolled
For each event, a list of cells relevant to the event are captured as well. This is described here. The messages include a list of relevant cells and the present state of the Notebook. Cell contents that have been seen before get replaced with a cell 'ID' in order to save storage space, which allows for the state of the Notebook to be reconstructed at a later time. The reason I point that out is that there might be use cases where multiple schemas could be registered for a single event.
Please let me know if anyone has any questions regarding our use case.
The text was updated successfully, but these errors were encountered:
adpatter
changed the title
The purpose of this Issue is just to give an example use case that will be deployed this Fall.
The purpose of this Issue is just to give an example use case.
Jul 22, 2021
Our telemetry project, ETC JupyterLab Telemetry Extension, captures user interactions and logs these messages to a specified handler. The ETC JupyterLab Telemetry Example repo gives an example of the service provided by the extension being consumed and the events being logged to
console.log
.Presently, we are capturing several user interactions with the Notebook:
For each event, a list of cells relevant to the event are captured as well. This is described here. The messages include a list of relevant cells and the present state of the Notebook. Cell contents that have been seen before get replaced with a cell 'ID' in order to save storage space, which allows for the state of the Notebook to be reconstructed at a later time. The reason I point that out is that there might be use cases where multiple schemas could be registered for a single event.
This JSON schema matches the event messages:
Please let me know if anyone has any questions regarding our use case.
The text was updated successfully, but these errors were encountered: