rossoctl / rossoctl/cortex

Feature: Usage graph for COST, and other small improvements to Usage screen

Open
#1,060 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
13
Forks
40
Avg merge
12h 17m
Merged PRs (30d)
156

Description

The USAGE screen cycles between the Metrics TOKENS, REQUESTS, ERRORS, and LATENCY. The display below shows that it also knows about COST. That should be one of the metrics in the cycle.

Also

  • The Units don't display on the vertical access or anywhere else, even though there is room.
  • The Session ID appears twice, even though it doesn't need to
  • The Sort order, e.g. [sort: TIME▼] appears, even though it has no meaning on this screen
  • There is an indication of 1.0 ev/s drops: 0, but I don't know what they mean
    • Claude says "drops is dead — it can only ever display 0"
    • weather-agent/demo-with-abctl.md: says "The bottom-footer rate indicator (3.2 ev/s) is a live smoothed events-per-second gauge — useful to tell if traffic is flowing or something upstream is stuck."

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the USAGE screen renderer and the code that cycles through TOKENS, REQUESTS, ERRORS, and LATENCY; also read weather-agent/demo-with-abctl.md for the event-rate indicator context. Done means COST appears in the cycle and the requested units, Session ID, sort order, and rate/drop indicators are reviewed and adjusted as specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.