Skip to main content

Kedro-Telemetry

Project description

Kedro-Telemetry

Python Version PyPI version License Code Style: Black

What is kedro-telemetry?

Kedro-Telemetry is a plugin that gathers anonymised and aggregated usage analytics to help the Kedro team understand how Kedro is used and prioritise improvements to the product accordingly.

What data is being collected?

Read our Telemetry documentation for further information on the intent of the data collection and what data is collected.

For technical information on how the telemetry collection works, you can browse the source code of kedro-telemetry.

How is the data collected

Kedro-Telemetry uses pluggy hooks and requests to send data to Heap Analytics. Project maintainers have access to the data and can create dashboards that show adoption and feature usage.

How do I withdraw consent?

Data collection for telemetry is enabled by default. To withdraw consent, you have a few options:

  1. Set Environment Variables: Set the environment variables DO_NOT_TRACK or KEDRO_DISABLE_TELEMETRY to any value. The presence of any of these environment variables will disable telemetry for all Kedro projects in that environment and will override any consent specified in the .telemetry file of the specific project.

  2. CLI Option When Creating a New Project: When creating a new project, you can use the command:

    kedro new --telemetry=no
    

    This will create a new project with a .telemetry file in its root folder, containing consent: false. This file will be used when executing Kedro commands within that project folder. Note that telemetry data about the execution of the kedro new command will still be sent if telemetry has not been disabled using environment variables.

    Note: The .telemetry file should not be committed to git or packaged in deployment. In kedro>=0.17.4 the file is git-ignored.

  3. Modify or Create the .telemetry file manually: If the .telemetry file exists in the root folder of your Kedro project, set the consent variable to false. If the file does not exist, create it with the following content:

    consent: false
    
  4. Uninstall the plugin: Remove the kedro-telemetry plugin:

    pip uninstall kedro-telemetry
    

    Note: This is a last resort option, as it will break the dependencies of Kedro (for example, pip check will report issues).

What happens when I withdraw consent?

If you explicitly deny consent from the beginning, no data will be collected. If you withdraw consent later, the processing of data will be stopped from that moment on.

What licence do you use?

Kedro-Telemetry is licensed under the Apache 2.0 License.

Python version support policy

  • The Kedro-Telemetry supports all Python versions that are actively maintained by the CPython core team. When a Python version reaches end of life, support for that version is dropped from kedro-telemetry. This is not considered a breaking change.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

kedro_telemetry-0.6.3.tar.gz (15.5 kB view details)

Uploaded Source

Built Distribution

kedro_telemetry-0.6.3-py3-none-any.whl (9.5 kB view details)

Uploaded Python 3

File details

Details for the file kedro_telemetry-0.6.3.tar.gz.

File metadata

  • Download URL: kedro_telemetry-0.6.3.tar.gz
  • Upload date:
  • Size: 15.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for kedro_telemetry-0.6.3.tar.gz
Algorithm Hash digest
SHA256 0fe452af6eac2723da7fd1d62cb1551db3e78ccd7b7e16539af440db545c47bf
MD5 c0ceed8e1bfe07112f0230926467c70a
BLAKE2b-256 9c0c113551b40fec9ecf0eb49bdd481b0e9a9ff983036135c7ea7b08e45d5704

See more details on using hashes here.

File details

Details for the file kedro_telemetry-0.6.3-py3-none-any.whl.

File metadata

File hashes

Hashes for kedro_telemetry-0.6.3-py3-none-any.whl
Algorithm Hash digest
SHA256 115c214092d186415f1e590550ae49bc8befabe2101b6961aac89a7e52be4a30
MD5 6bbc0c0a0623479cc921195ccdbb25b9
BLAKE2b-256 77130bd01dfe5b38f54cd20fbda4179b2fb9c4d2ab8c12ab3ac571b68b6e6ba4

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page