docs: fix paths example under “Restricting a Metric to Specific Log Files” #196
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.
This PR corrects a documentation example that showed paths with a single scalar string. In the grok_exporter config schema, paths must be a YAML list ([]string). For a single glob, either use path (single string) or keep paths as a one‑item list. The current example can mislead users and cause YAML/schema validation errors at startup.
Problem
The docs currently show:
pathsis defined in the config as a list of strings (see the PathsAndGlobs struct: Path string, Paths []string).pathscan yield errors likecannot unmarshal !!str into []stringor simply fail validation, depending on the parser/version.