Telemetry

As an open source project, we collect usage statistics to inform development priorities. Telemetry data will motivate projects such as adding features in frequently-used parts of the CLI and adding more examples in the docs in areas where users encounter more errors.

For example, we monitor the error rate of dagster execute pipeline invocations to help us ensure our programming model is intuitive to use and to catch docs regressions.

We will not see or store solid definitions (including generated context) or pipeline definitions (including modes and resources). We will not see or store any data that is processed within solids and pipelines.

The telemetry-instrumented functions are:

telemetry.py

1
2
3
4
5
TELEMETRY_WHITELISTED_FUNCTIONS = {
    'pipeline_execute_command',
    'pipeline_launch_command',
    'execute_pipeline',
}

To see the logs we send, open $DAGSTER_HOME/logs/ if $DAGSTER_HOME is set or ~/.dagster/logs/ if not set (after calling the instrumented functions).

If you'd like to opt-out, you can add the following to $DAGSTER_HOME/dagster.yaml (creating that file if necessary):

telemetry:
  enabled: false