Jupyterlab-pioneer NPM

JupyterLab Pioneer

A JupyterLab extension for generating and exporting JupyterLab event telemetry data.

Get started

Run the extension with docker compose

# enter the configuration_examples directory and run
docker compose -p jupyterlab_pioneer up --build

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

(To play with different exporter configurations, edit Dockerfile and run docker compose again)

Or install the extension and configure it manually

To install the extension, execute:

pip install jupyterlab_pioneer

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

Examples of configurations are here.

Configurations

Overview

The configuration file controls the activated events and data exporters.

To add a data exporter, users should assign a callable function along with function arguments when configuring exporters.

This extension provides 5 default exporters.

console_exporter, which sends telemetry data to the browser console
command_line_exporter, which sends telemetry data to the python console jupyter is running on
file_exporter, which saves telemetry data to local file
remote_exporter, which sends telemetry data to a remote http endpoint
opentelemetry_exporter, which sends telemetry data via otlp.

Additionally, users can write customized exporters in the configuration file.

Configuration file name & path

Jupyter Server expects the configuration file to be named after the extension’s name like so: jupyter_{extension name defined in application.py}_config.py. So, the configuration file name for this extension is jupyter_jupyterlab_pioneer_config.py.

Jupyter Server looks for an extension’s config file in a set of specific paths. The configuration file should be saved into one of the config directories provided by jupyter --path.

Check jupyter server doc for more details.

Syntax

activateEvents: An array of active events. Each active event in the array should have the following structure:

{
    'name': # string, event name
    'logWholeNotebook': # boolean, whether to export the entire notebook content when event is triggered
}

The extension would only generate and export data for valid event that has an id associated with the event class, and the event name is included in activeEvents. The extension will export the entire notebook content only for valid events when the logWholeNotebook flag is True.

exporters: An array of exporters. Each exporter in the array should have the following structure:

{
    'type': # One of 'console_exporter', 'command_line_exporter',
            # 'file_exporter', 'remote_exporter',
            # or 'custom_exporter'.
    'args': # Optional. Arguments passed to the exporter function.
            # It needs to contain 'path' for file_exporter, 'url' for remote_exporter.
    'activeEvents': # Optional. Exporter's local activeEvents config will override global activeEvents config
}

Example

Default exporters

all_exporters/jupyter_jupyterlab_pioneer_config.py

Custom exporter function

custom_exporter/jupyter_jupyterlab_pioneer_config.py

Uninstall

To remove the extension, execute:

pip uninstall jupyterlab_pioneer

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

Development install

(Optional) create conda environment from the provided `environment.yml` file

conda env create -f environment.yml

Clone and build the extension package

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-pioneer 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_pioneer
# 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_pioneer
pip uninstall jupyterlab_pioneer

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-pioneer within that folder.