Add docs for Connect usage reporting#21294
Conversation
| - Starting an SSH, database, or kube session | ||
| - File transfer during an SSH session | ||
| - Managing access requests | ||
| - Asking about job role |
There was a problem hiding this comment.
@ravicious I added "asking about job role" too. Although it is a slightly different type of event (it is not collected in the background, but rather asked explicitly) I think it makes sense to have it on the list.
| @@ -0,0 +1,18 @@ | |||
| When you first start the app, Teleport Connect asks for permission to collect & send telemetry data. | |||
| This includes tracking events such as: | |||
| - Login | |||
There was a problem hiding this comment.
| - Login | |
| - Logging in to Teleport |
Assuming this is correct (making it more specific)
There was a problem hiding this comment.
Maybe Logging in to a cluster?
| - Login | ||
| - Starting an SSH, database, or kube session | ||
| - File transfer during an SSH session | ||
| - Managing access requests |
There was a problem hiding this comment.
Does this include creating an Access Request as well as other events in the Access Request lifecycle?
There was a problem hiding this comment.
It includes two events: creating and reviewing an Access Request.
There was a problem hiding this comment.
👍 I think it would make sense to list both of these separately
There was a problem hiding this comment.
Three events actually, assuming an access request is reported as well.
There was a problem hiding this comment.
Good catch, I forgot about it.
| - Starting an SSH, database, or kube session | ||
| - File transfer during an SSH session | ||
| - Managing access requests | ||
| - Asking about job role |
There was a problem hiding this comment.
Is there another way to put this? This is the only instance of "job role" in the docs, and it would be good to be more consistent with other pages:
$ grep -Rni "job role" docs/pages
docs/pages/includes/teleport-connect-telemetry.mdx:7:- Asking about job role
There was a problem hiding this comment.
Any suggestions?
We ask users about it to get a list of job roles for people who are using Teleport Connect. Nothing better than "job role" comes to my mind 😏
There was a problem hiding this comment.
Ah, that make sense. I wasn't sure what context to use for interpreting "job role". Maybe something like, "Indicating when Teleport Connect asks a user to describe their role at their organization"?
Are all the items in this list events that Teleport Connect tracks? If the job title item isn't, I think we should separate it from this list.
There was a problem hiding this comment.
Ah, I realized that including "job role" it the list is confusing, because the event is not intended to indicate that the user was asked, we collect the user's response itself.
What do you think of adding a line below - Processor architecture:
Additionally, we ask for a job role (answer is optional).
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
|
@ptgott I pushed all the changes, please take a look at the final version 🙏 |
|
|
||
| ### Disabling telemetry | ||
|
|
||
| If you initially agreed to share telemetry data, but now want to opt out, you need to update the `app_config.json` file: |
There was a problem hiding this comment.
Does the app need to be closed first? I don't remember if we dump the current config to the file just like we do with app_state.json.
There was a problem hiding this comment.
No, it doesn't. The config file is updated only on change.
|
I suppose the backport to v12 should wait until we actually track that data in v12, right? |
Yes. |
* Add docs for Connect usage reporting * reuse telemetry specifics in partial file * copy edits * Apply suggestions from code review Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com> * Add Zac's suggestion Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com> * Apply suggestions * Add "Assuming an Access Request" --------- Co-authored-by: alexfornuto <alex.fornuto@goteleport.com> Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com> Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
Backport to v12 when we enable it in Connect (and add a link in the dialog to the docs).