Skip to content

docs(cli): correct the dora top note about what each metric column means - #3111

Draft
phil-opp wants to merge 1 commit into
mainfrom
claude/dreamy-bardeen-xphg86-top-metrics-doc
Draft

docs(cli): correct the dora top note about what each metric column means#3111
phil-opp wants to merge 1 commit into
mainfrom
claude/dreamy-bardeen-xphg86-top-metrics-doc

Conversation

@phil-opp

Copy link
Copy Markdown
Collaborator

Issue

The dora top help note (binaries/cli/src/command/inspect/top.rs) states:

/// Note:
/// - Values are averaged over the last refresh period

That is inaccurate for most of the table. Verified against the data source:

  • NET TX / NET RXnet_bytes_sent / net_bytes_received are monotonic counters that are only ever fetch_add-ed and never reset (running_dataflow.rs, incremented in daemon/src/lib.rs). They are lifetime cumulative totals, not per-period averages.
  • RESTARTS is a cumulative count; QUEUE (pending messages) and MEMORY (MB) are point-in-time snapshots; CPU% is an instantaneous sample.
  • Only I/O READ / I/O WRITE are a per-refresh-interval rate.

Under the old wording, a steadily growing cumulative "NET TX" reads as an ever-rising throughput.

Fix

Reword the note to state per-column semantics accurately (instantaneous vs. per-interval rate vs. cumulative/point-in-time). Documentation only — no behavior change.

Validation

cargo fmt --all -- --check
cargo clippy -p dora-cli -- -D warnings

(Doc-comment-only change to a clap Args help string.)


⚠️ This is a machine-generated PR authored by Claude (Claude Code) as part of an automated codebase review. The finding was verified by hand against origin/main before opening. Please review carefully before merging.

🤖 Generated with Claude Code


Generated by Claude Code

…means

The header note claimed "Values are averaged over the last refresh
period", but that is only true for the disk-I/O columns. Verified against
the data source:

- NET TX / NET RX are monotonic counters (`fetch_add`-ed, never reset in
  the daemon) — lifetime cumulative totals, not per-period averages.
- RESTARTS is a cumulative count; QUEUE and MEMORY are point-in-time
  snapshots; CPU% is an instantaneous sample.
- Only I/O READ / I/O WRITE are a per-refresh-interval rate.

A steadily growing cumulative "NET TX" read as an ever-rising throughput
under the old wording. Reword the note to state per-column semantics
accurately. Documentation only; no behavior change.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PYiYgEo2WKBXfGooqP2WG5
@trunk-io

trunk-io Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

Copy link
Copy Markdown
Collaborator Author

🤖 Automated review by Claude — this is a fully automated review with no human in the loop. Treat it as advisory.

Reviewed the diff — documentation-only change to the dora top header note, and the new per-column semantics (instantaneous CPU/MEMORY, per-interval I/O rates, cumulative NET TX/RX/RESTARTS, current QUEUE) match how those columns are actually computed. No issues found.


Generated by Claude Code

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants