Skip to content

Spike: CLI-side telemetry #95

Description

@khvn26

Examples of deeper insight we'll gain with client-side telemetry:

  • approximate token costs per command
  • % of --jq usage
  • % of JSON output used
  • % of usage errors

The client-side telemetry needs to be opt-in. We should:

  • design the user-facing part of the experience, and update the design docs.
  • decide on the transport/infra, and come up with an epic.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions