We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug The documentation is inconsistent as to whether new installations should use v10 or v11 schema.
To Reproduce At https://github.com/grafana/loki/blob/master/docs/architecture.md it says:
The current schema recommendation is the v10 schema.
But in the sample loki configuration at https://github.com/grafana/loki/blob/master/cmd/loki/loki-local-config.yaml it says
schema: v11
Expected behavior If the current schema recommendation is the v10 schema, then I'd expect the sample config to use the v10 schema too.
Environment: N/A
Screenshots, Promtail config, or terminal output N/A
The text was updated successfully, but these errors were encountered:
hey @candlerb thanks for bringing this up.
v11 is the recommended schema, would you be interested in a PR to fix the docs?
Sorry, something went wrong.
Recommended schema is now v11
a2d1aba
Fixes grafana#1778 Signed-off-by: Brian Candler <b.candler@pobox.com>
f106c09
Fixes #1778 Signed-off-by: Brian Candler <b.candler@pobox.com>
Successfully merging a pull request may close this issue.
Describe the bug
The documentation is inconsistent as to whether new installations should use v10 or v11 schema.
To Reproduce
At https://github.com/grafana/loki/blob/master/docs/architecture.md it says:
But in the sample loki configuration at https://github.com/grafana/loki/blob/master/cmd/loki/loki-local-config.yaml it says
Expected behavior
If the current schema recommendation is the v10 schema, then I'd expect the sample config to use the v10 schema too.
Environment:
N/A
Screenshots, Promtail config, or terminal output
N/A
The text was updated successfully, but these errors were encountered: