Skip to main content

JupyterLab Telemetry Producer

PyPI npm

A JupyterLab extension for generating telemetry data with a basic JupyterLab event library.

This extension relies on the jupyterlab-telemetry-router extension.

Get started

Run the telemetry system with docker compose

# enter the configuration_example directory and run
docker compose -p jupyterlab-telemetry up --build

A JupyterLab application with the telemetry system installed and configured will run on localhost:8888.

Or install the extension and configure it manually

To install the extension, execute:

pip install jupyterlab-telemetry-producer

The jupyterlab-telemetry-router extension is automatically installed when jupyterlab-telemetry-producer is installed.

Before starting Jupyter Lab with the telemetry system, users need to write their own producer/router configuration files (or use provided configuration examples) and place them in the correct directory.

Examples of producer configurations are here.

Examples of router configurations are here.

Basic JupyterLab Event Library

Overview

Event Producer ID Event Triggered When Event Data Structure
NotebookOpenEvent a notebook is opened eventName, eventTime, environ: current environment data
NotebookScrollEvent user scrolls on the notebook eventName, eventTime, cells: visible cells after scrolling
NotebookVisibleEvent user navigates back to Jupyter Lab eventName, eventTime, cells: visible cells when user navigates back
NotebookHiddenEvent user leaves the Jupyter Lab tab eventName, eventTime
ClipboardCopyEvent user copies from a notebook cell eventName, eventTime, cells: cell copied from, selection: copied text
ClipboardCutEvent user cuts from a notebook cell eventName, eventTime, cells: cell cut from, selection: cut text
ClipboardPasteEvent user pastes to a notebook cell eventName, eventTime, cells: cell pasted to, selection: pasted text
ActiveCellChangeEvent user moves focus to a different cell eventName, eventTime, cells: activated cell
NotebookSaveEvent a notebook is saved eventName, eventTime
CellExecuteEvent a cell is executed eventName, eventTime, cells: executed cell, success, kernelError: error detail if execution failed
CellAddEvent a new cell is added eventName, eventTime, cells: added cell
CellRemoveEvent a cell is removed eventName, eventTime, cells: removed cell

Configurations

Syntax

activateEvents: required. An array of the ids of the events. Only valid event producers (1. has an id associated with the event producer class, and 2. the event id is included in activatedEvents) will be activated.

logNotebookContentEvents: required. An array of the ids of the events. Only valid event producers (1. has an id associated with the event producer class, and 2. the event id is included in logNotebookContentEvents) will have the router export the entire notebook content along with the event data.

The configuration file should be saved into one of the config directories provided by jupyter --path.

Example

c.JupyterLabTelemetryProducerApp.activeEvents = [
    'NotebookOpenEvent',
    'NotebookScrollEvent',
    # 'NotebookVisibleEvent',
    # 'NotebookHiddenEvent',
    'ClipboardCopyEvent',
    'ClipboardCutEvent',
    'ClipboardPasteEvent',
    'ActiveCellChangeEvent',
    'NotebookSaveEvent',
    'CellExecuteEvent',
    'CellAddEvent',
    'CellRemoveEvent',
]

c.JupyterLabTelemetryProducerApp.logNotebookContentEvents = [
    'NotebookOpenEvent',
    # 'NotebookScrollEvent',
    # 'NotebookVisibleEvent',
    # 'NotebookHiddenEvent',
    # 'ClipboardCopyEvent',
    # 'ClipboardCutEvent',
    # 'ClipboardPasteEvent',
    # 'ActiveCellChangeEvent',
    'NotebookSaveEvent',
    # 'CellExecuteEvent',
    # 'CellAddEvent',
    # 'CellRemoveEvent',
]

Uninstall

To remove the extension, execute:

pip uninstall jupyterlab-telemetry-producer

Troubleshoot

If you are seeing the frontend extension, but it is not working, check that the server extension is enabled:

jupyter server extension list

If the server extension is installed and enabled, but you are not seeing the frontend extension, check the frontend extension is installed:

jupyter labextension list

Contributing

To write your own telemetry producer extensions, a tutorial with a simple demo could be find here.

Development install

Note: You will need NodeJS to build the extension package.

The jlpm command is JupyterLab's pinned version of yarn that is installed with JupyterLab. You may use yarn or npm in lieu of jlpm below.

# Clone the repo to your local environment
# Change directory to the jupyterlab-telemetry-producer directory
# Install package in development mode
pip install -e "."
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Server extension must be manually installed in develop mode
jupyter server extension enable jupyterlab-telemetry-producer
# Rebuild extension Typescript source after making changes
jlpm build

You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.

# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm watch
# Run JupyterLab in another terminal
jupyter lab

With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).

By default, the jlpm build command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:

jupyter lab build --minimize=False

Development uninstall

# Server extension must be manually disabled in develop mode
jupyter server extension disable jupyterlab-telemetry-producer
pip uninstall jupyterlab-telemetry-producer

In development mode, you will also need to remove the symlink created by jupyter labextension develop command. To find its location, you can run jupyter labextension list to figure out where the labextensions folder is located. Then you can remove the symlink named jupyterlab-telemetry-producer within that folder.

Packaging the extension

See RELEASE

Metadata

Release files for jupyterlab-telemetry-producer 0.1.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jupyterlab-telemetry-producer 0.1.7
File Size Uploaded Provenance Actions
jupyterlab_telemetry_producer-0.1.7.tar.gz 97.3 kB Without provenance Details for jupyterlab_telemetry_producer-0.1.7.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for jupyterlab-telemetry-producer 0.1.7
File Interpreter ABI Platform Actions
jupyterlab_telemetry_producer-0.1.7-py3-none-any.whl Python 3 none any Details for jupyterlab_telemetry_producer-0.1.7-py3-none-any.whl

Total release size: 117.5 kB

Release files / jupyterlab_telemetry_producer-0.1.7.tar.gz

Download URL jupyterlab_telemetry_producer-0.1.7.tar.gz
Size 97.3 kB
Tags Source
SHA-256 checksum
How to use checksums
c340aae0b68db583cf7d0d3b1aa8965dfd896e6529ba792144dfe1c8c9263f23
BLAKE2b-256 checksum
How to use checksums
8ea7a2ec0faf4a02225b3b889e1ee3efeaf40e964f05ecd0d7ebb181aaf60986
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.11.5

Release files / jupyterlab_telemetry_producer-0.1.7-py3-none-any.whl

Download URL jupyterlab_telemetry_producer-0.1.7-py3-none-any.whl
Size 20.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
af6b5a7e9781e2b8992cb76d0406ab418bda8eebb61fbe1aa8218ff2375b51ab
BLAKE2b-256 checksum
How to use checksums
1fba73ec6ff330518ac27b56f24ff8971ce9647db767a0f099eb83d0afe9dd94
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.11.5

Security for jupyterlab-telemetry-producer 0.1.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page