[DOCS-4930] Add --order and --range flags to machines logs CLI reference - #5263
Merged
Jeremy Rose (jeremyrose-viam) merged 3 commits intoAug 19, 2026
Merged
Conversation
The RDK CLI (rdk#6337) added --order (asc/desc) and --range (e.g. 10m, 10h, 10d) flags to the viam machines logs command for relative time windows and sort control. Update the CLI reference flag table and add usage examples to the troubleshooting guide. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015iCdDmnptAMYXX6DeXrEEP
✅ Deploy Preview for viam-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
viambot
added
the
safe to build
10zingpd
changed the title
Jeremy Rose (jeremyrose-viam)
approved these changes
Aug 19, 2026
Jeremy Rose (jeremyrose-viam)
left a comment
Jeremy Rose (jeremyrose-viam)
left a comment
Contributor
There was a problem hiding this comment.
Confirmed released in CLI 1.4.0.
Jeremy Rose (jeremyrose-viam)
deleted the
claude/add-cli-logs-order-range-flags
branch
August 19, 2026 16:27
|
🔎💬 Inkeep AI search and chat service is syncing content for source 'Viam Docs' |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The RDK CLI gained
--orderand--rangeflags on theviam machines logscommand (viamrobotics/rdk#6337), backed by the proto-levelorderandrangefields added toGetRobotPartLogsRequest(viamrobotics/api#888) and the app backend implementation (viamrobotics/app#13101, viamrobotics/app#13122).Summary
--rangeand--orderto themachines logsflag table in CLI reference--startdefault text to note it is overridden when--rangeis set--rangeand--orderSource changes
--orderand--rangeflags formachines logsrdk#6337: Add--orderand--rangeflags formachines logsorderandrangefields toGetRobotPartLogsRequestapi#888: AddLogOrderenum,orderandrangefields toGetRobotPartLogsRequest--rangeand--orderfrom CLI logs export command in app UIDocs changes
docs/cli/reference.md: Added--rangeand--orderrows to themachines logsflag table; updated--startdefault textdocs/monitor/troubleshoot.md: Added two examples showing relative time window (--range 2h) and oldest-first ordering (--order asc)How I found these
api-af2e9b6-log-order-rangewas deferred "until CLI flags or SDK wrappers ship" — CLI flags shipped in rdk#6337--orderand--rangewere not documented anywhere in the docs repoGenerated by daily docs change agent
Generated by Claude Code