Description
The product advertises automatic target discovery, but the node-metrics guide teaches only static targets. Add a complete discovery-first path without displacing the static configuration.
Acceptance Criteria
- #1 The guide includes valid discovery-only YAML with enabled plus discovery settings
- #2 It explains the online, non-external, tag, address-family, port, and maximum-target defaults
- #3 It states the client-metrics endpoint and ACL prerequisites and how discovered and static targets combine
- #4 A first-success query confirms discovered targets and forwarded metrics
Definition of Done
- #1 go build ./… && go vet ./… && go test -race ./…
- #2 golangci-lint run
- #3 scripts/regen-generated.sh (only if a generated artifact’s inputs changed)
Implementation Plan
Add a discovery-first node-metrics path from live config defaults, preserving static targets and documenting a first-success query.
Implementation Notes
Discovery-first configuration, defaults, prerequisites, and first-success query are committed in bundled pause snapshot 2cf46446d5c6a7a30ea6f7d0c54d61ec9889d522. Resume with exact-head CI and live documentation verification.
Final evidence: documentation checker, integrated GATE, and exact-head CI run 33047209645 passed. The deployed exporter continued emitting node and device telemetry while the new discovery-first guide remained consistent with source defaults.
Final Summary
Dynamic node-metrics discovery guidance is committed in 2cf46446d5c6a7a30ea6f7d0c54d61ec9889d522; parked pending CI and live verification.
Completion: verified by documentation checks, full gate, and exact-head CI.