Spike: CLI-side telemetry

Open
#95 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
go
Domain
cli, observability

Research direction

Start by reviewing the existing design docs and the CLI's telemetry-related entry points, if any. Define the opt-in user experience, document it, and evaluate transport and infrastructure options. The work is done when the design docs are updated and a follow-up epic captures the agreed implementation.

Written by the indexing model from the issue text.

Description

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.
Dominant language
Go
Stars
12
Forks
3
Avg merge
14h 56m
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Flagsmith/flagsmith-cli

All issues in Flagsmith/flagsmith-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.