You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to anonymously track real usage of the CLI. Whenever a command is run, we could post to some tracking service with the basic details (maybe we can include the final run status and time too?)
We should do this in a non annoying and non invasive way. I don't know if we need a GDPR expert to weigh in.
Ideally it would be opt out, so that we get tracking by default. We'll need to tell users this clearly on install. I also wonder if we should have debug logs like posting anonymous metric with command name, runtime, and exit code whenever we post a metric. Or maybe a better approach is, if metrics are enabled:
always log a message like "Anonymous usage metric reporting is enabled. See for details"
Then maybe debug log exactly what is sent in each request
That feels like a good balance of being clear but not annoying. We can have an env var or option like OPENFN_DISABLE_METRIC_DISCLOSURE or something
To opt out, set an env var like OPENFN_DISABLE_METRICS. Lightning installs which use the CLI should do this (I suppose we could not add metrics to the metadata task, which I think is all that lightning uses the CLI for now?).
It might be nice to have a .openfnrc in the working folder to provide options like this. And maybe a default one in the repo too. Then users can do openfn set metrics false or something to set the option on their machine without using an env var (idk why this is valuable though)
Where to we report metrics to? Grafana?
The text was updated successfully, but these errors were encountered:
It would be great to anonymously track real usage of the CLI. Whenever a command is run, we could post to some tracking service with the basic details (maybe we can include the final run status and time too?)
We should do this in a non annoying and non invasive way. I don't know if we need a GDPR expert to weigh in.
Ideally it would be opt out, so that we get tracking by default. We'll need to tell users this clearly on install. I also wonder if we should have debug logs like
posting anonymous metric with command name, runtime, and exit code
whenever we post a metric. Or maybe a better approach is, if metrics are enabled:always
log a message like "Anonymous usage metric reporting is enabled. See for details"debug
log exactly what is sent in each requestThat feels like a good balance of being clear but not annoying. We can have an env var or option like
OPENFN_DISABLE_METRIC_DISCLOSURE
or somethingTo opt out, set an env var like
OPENFN_DISABLE_METRICS
. Lightning installs which use the CLI should do this (I suppose we could not add metrics to the metadata task, which I think is all that lightning uses the CLI for now?).It might be nice to have a
.openfnrc
in the working folder to provide options like this. And maybe a default one in the repo too. Then users can doopenfn set metrics false
or something to set the option on their machine without using an env var (idk why this is valuable though)Where to we report metrics to? Grafana?
The text was updated successfully, but these errors were encountered: