Need to provide the same functionality as java lib
It also make sense to provide a way to globally disable the telemetry in the current process with one call (and keep it disabled for subsequent calls/initializations) without necessity to set the environment variable.
Overall, make sense to refactor the API, as it is going to be the breaking change anyways:
- get rid of
setup, initialize the telemetry on first track request
- provide software name and version, handle them properly for multi-package scenarios (by sending separate json messages)
- add
disable() call, which disables telemetry in a sticky way (is needed for DBT support)
- add environment variable to enable telemetry logging (to simplify the integration testing + possible troubleshooting)
Need to provide the same functionality as java lib
It also make sense to provide a way to globally disable the telemetry in the current process with one call (and keep it disabled for subsequent calls/initializations) without necessity to set the environment variable.
Overall, make sense to refactor the API, as it is going to be the breaking change anyways:
setup, initialize the telemetry on firsttrackrequestdisable()call, which disables telemetry in a sticky way (is needed for DBT support)