Skip to content

Add docs for Connect usage reporting#21294

Merged
gzdunek merged 9 commits into
masterfrom
gzdunek/connect-usage-reporting-docs
Feb 8, 2023
Merged

Add docs for Connect usage reporting#21294
gzdunek merged 9 commits into
masterfrom
gzdunek/connect-usage-reporting-docs

Conversation

@gzdunek
Copy link
Copy Markdown
Contributor

@gzdunek gzdunek commented Feb 6, 2023

Backport to v12 when we enable it in Connect (and add a link in the dialog to the docs).

Comment thread docs/pages/faq.mdx Outdated
- Starting an SSH, database, or kube session
- File transfer during an SSH session
- Managing access requests
- Asking about job role
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

@alexfornuto alexfornuto self-assigned this Feb 6, 2023
Copy link
Copy Markdown
Contributor

@alexfornuto alexfornuto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved, but should not be merged (or at least not backported) yet per the comment below.

Comment thread docs/pages/includes/teleport-connect-telemetry.mdx Outdated
@alexfornuto alexfornuto removed their assignment Feb 6, 2023
Comment thread docs/pages/includes/teleport-connect-telemetry.mdx Outdated
@@ -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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Login
- Logging in to Teleport

Assuming this is correct (making it more specific)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe Logging in to a cluster?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works for me!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Comment thread docs/pages/includes/teleport-connect-telemetry.mdx Outdated
Comment thread docs/pages/includes/teleport-connect-telemetry.mdx Outdated
- Login
- Starting an SSH, database, or kube session
- File transfer during an SSH session
- Managing access requests
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this include creating an Access Request as well as other events in the Access Request lifecycle?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It includes two events: creating and reviewing an Access Request.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 I think it would make sense to list both of these separately

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Three events actually, assuming an access request is reported as well.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 😏

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That sounds good to me!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Comment thread docs/pages/includes/teleport-connect-telemetry.mdx Outdated
Comment thread docs/pages/includes/teleport-connect-telemetry.mdx Outdated
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Comment thread docs/pages/connect-your-client/teleport-connect.mdx Outdated
@gzdunek
Copy link
Copy Markdown
Contributor Author

gzdunek commented Feb 7, 2023

@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:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it doesn't. The config file is updated only on change.

@ravicious
Copy link
Copy Markdown
Member

I suppose the backport to v12 should wait until we actually track that data in v12, right?

@gzdunek
Copy link
Copy Markdown
Contributor Author

gzdunek commented Feb 8, 2023

I suppose the backport to v12 should wait until we actually track that data in v12, right?

Yes.

@gzdunek gzdunek added this pull request to the merge queue Feb 8, 2023
Merged via the queue into master with commit e8de43e Feb 8, 2023
@public-teleport-github-review-bot
Copy link
Copy Markdown

@gzdunek See the table below for backport results.

Branch Result
branch/v12 Create PR

avatus pushed a commit that referenced this pull request Mar 3, 2023
* 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>
@gzdunek gzdunek deleted the gzdunek/connect-usage-reporting-docs branch March 20, 2023 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants