tursodatabase/turso-cli

`turso db inspect` should show more than just space

Open

#303 opened on Mar 27, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (50 forks)github user discovery
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (302 stars)
PR merge metrics
 (PR metrics pending)

Description

Follow up from #275, users will want to know more than their storage used. We need to show:

  • bandwidth used (per day, per month, total)
  • rows read (per day, per month, total)

This info should also be split on a per-location basis, so users can know which of their locations are seeing more activity than the rest

Contributor guide

Research direction
Examine the existing `db inspect` implementation in the turso cli codebase, and identify the Turso API endpoints that provide bandwidth and rows read metrics per location. Then implement the new fields and display them in the output.
Tech stack
go
Domain
backendcli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoTurso CLI knowledgeFamiliarity with Turso API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60