Conversation
9f09be4 to
e9587f7
Compare
f9a50b5 to
af7d77f
Compare
craicoverflow
left a comment
There was a problem hiding this comment.
Reviewed a bit and verified from CLI side. Tomorrow I will look at the analytics dashboard.
Question: what if the user changes their mind and wants to later opt-out? Should be be providing an easy way to opt-out again?
ODO and other commands have config comand that allow to change config. I think if you want to turn it off you should set env variable |
Do users know about this environment variable to do so if they wish? |
|
USAGE_DATA.md contains some info about it. Can we put it in other places? |
How many customers will look at this repo to finds that out? Should it be included as part of the confirmation message when opting in? |
Would do |
craicoverflow
left a comment
There was a problem hiding this comment.
Errors don't seem to be logged (comment left inline)
|
To verify you would need to build production version (non dev) or.. use environment variable. I think initially we can release this feature enabled only in dev mode and after legal enables us to collect details we can switch to all users. |



Telemetry commands
Challenges
Asking users to comply with analytics on first usage
https://developers.redhat.com/article/tool-data-collection
Preventing counting internal usage
Preventing sending usage for meta commands
__completion, help etc. should not send analytics