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

feat: telemetry for all commands #366

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

feat: telemetry for all commands #366

wants to merge 3 commits into from

Conversation

neurosnap
Copy link
Member

This change will make it so all commands run with aptible-cli will send a tuna event with the following info:

  • user email
  • user -or- org id
  • format (e.g. text or json)
  • command run
  • options provided to command

This is the foundation for us to evaluate usage and provide us with the ability to make decisions about the future direction of the CLI.

I tried to find a before hook for Thor but it looks like it doesn't exist: https://stackoverflow.com/questions/61855861/is-there-a-way-to-add-hooks-to-a-thor-class-in-order-to-run-code-before-after-al

This change will make it so all commands run with `aptible-cli` will
send a tuna event with the following info:

- user email
- user -or- org id
- format (e.g. text or json)
- command run
- options provided to command

This is the foundation for us to evaluate usage and provide us with the
ability to make decisions about the future direction of the CLI.

I tried to find a `before` hook for Thor but it looks like it doesn't
exist: https://stackoverflow.com/questions/61855861/is-there-a-way-to-add-hooks-to-a-thor-class-in-order-to-run-code-before-after-al
Copy link
Member

@UserNotFound UserNotFound left a comment

Choose a reason for hiding this comment

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

Does this actually work with httpclient? I get SSL verification errors when i bundle exec it from source, and i also just hacked this change into my toolbelt version, and get the same certificate verify failed error, even though this is a valid let's encrypt certificate? We don't use LE certs for auth.aptible.com or api.aptible.com (the other endpoints the CLI talks to) so i don't know exactly what is to blame here:

Screenshot 2025-01-30 at 15 24 52

You could bump the version in this PR if you don't want to open another one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants