influxdata/telegraf

CLI documentation

Open

#15,871 opened on Sep 11, 2024

View on GitHub
 (1 comment) (1 reaction) (1 assignee)Go (9,892 stars) (4,161 forks)batch import
feature requesthelp wantedsize/m

Description

Use Case

It would be nice to have a human readable documentation about the CLI command and all possible sub-commands + options in the repository. Just like we have a README.md for every plugin.

Expected behavior

Having a readme file in cmd/telegraf/ directory which not only says to run telegraf help but also has the actual documentation of the various commands and flags.

Actual behavior

Currently one needs to download/install telegraf binary and run its help command in order to read about a certain functionality.

Additional info

Could be autogenerated by running the make docs command. The CI could then warn the contributor if the repo is dirty and need to push the updated docs.

Contributor guide

Tech stack
goshell
Domain
documentation
Issue type
documentation
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.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingCLI documentationMakefile usageCI basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
The issue requests adding a CLI documentation readme in `cmd/telegraf/`. Investigate the current `make docs` command (likely in the Makefile) to understand how documentation is autogenerated. Look at existing README files for plugins as a template. Also examine the CI configuration (e.g., GitHub Actions) to see how to add a check for dirty repo on docs generation. The assignee may have started work, so check recent activity in the repository.