oxidecomputer / oxidecomputer/dendrite

rmon counter read is less than ergonomic

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

Nobody has claimed this yet.

Dominant language
Rust
Stars
20
Forks
3
Avg merge
3d 11h
Merged PRs (30d)
4

Description

The swadm command to read the rmon counters can return varying levels of detail. One specifies that level with a -l option. There is nothing to indicate what legal -l values might be or what they might mean. If we want to keep the same "level of detail" model, we should specify it with multiple -v options, which is a fairly standard idiom. We could also just have a single -v which distinguishes between minimal and maximal detail.

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.

Research direction

Start at the swadm rmon counter command and inspect how the -l option is parsed and how its help text describes the available detail levels. Determine whether the project should adopt repeated -v options or a single -v switch; done means the chosen interface has clear, documented semantics and the command's behavior matches them.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.