Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TS-Disc-Control Discord - Verified Bot User & Telemetry Provider #18

Open
techy2493 opened this issue Feb 9, 2024 · 1 comment
Open
Labels
community input requested We need to know what the community thinks before addressing enhancement New feature or request

Comments

@techy2493
Copy link
Owner

techy2493 commented Feb 9, 2024

Telemetry is useful for developers to make sure we resolve the problems facing our users as soon as possible (sometimes before they even know they are having them).

In the TS-Disc-Control discord add two new roles. Verified Bot User, and Telemetry Provider.
In the bot itself, add a method by which we can verify a member of the TS-Disc-Control bot is running a bot (maybe a /verify command that pings the user's bot and checks that that user's ID is registered?? - need to do some thinking here to make it safe)
In the bot itself add a config to send telemetry to developers (always optional)

  • Send configured bot owner's Discord ID with telemetry and grant them Telemetry Provider role in discord
  • Send Telemetry
    • Bot Version
    • number of roles synced
    • number of users registered
    • number of users with more than one secondary ID
    • number of errors per day
    • Most common error per day
    • Non-sensitive config data (OAuth on/off, pokes or messages, etc.)
      • Will never contain any data from discord, or teamspeak, or database config elements probably move the stuff to a new config section
      • log exactly what is sent in each telemetry push

Create a logger to receive the telemetry.

@techy2493 techy2493 added enhancement New feature or request community input requested We need to know what the community thinks before addressing labels Feb 9, 2024
@techy2493
Copy link
Owner Author

Before implementing this I would like to know what people think. I know that telemetry and data collection can be heated topics, these are the metrics we'd collect if we were hosted and will help us decide on how we might provide hosting in the future. However I am aware some people might not be comfortable with these sort of features even if they were opt-in only. What are your thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community input requested We need to know what the community thinks before addressing enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant