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 When following the configuration reference, the comment above schema_config.configs[*].store says:
schema_config.configs[*].store
# Which store to use for the index. Either cassandra, bigtable, dynamodb, or # boltdb store: <string>
However, when running loki with dynamodb as the client, the following message is sent to the logs:
level=error ts=2019-11-19T00:52:11.372697769Z caller=main.go:65 msg="error initialising loki" err="error initialising module: table-manager: Unrecognized storage client dynamodb, choose one of: aws, cassandra, inmemory, gcp, bigtable, bigtable-hashed"
To Reproduce Steps to reproduce the behavior:
dynamodb
Expected behavior Starting up and using the dynamodb config was expected.
Environment:
Screenshots, Promtail config, or terminal output
The text was updated successfully, but these errors were encountered:
Hey @Tzrlk, it looks like that comment is wrong :(
https://github.com/cortexproject/cortex/blob/ed7c302fd96892b1c4c822a6ccd60317fde51c00/pkg/chunk/storage/factory.go#L182
Looks like you would need to use aws
aws
This is confusing, will leave this issue open to see if we can tidy this up some.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
When following the configuration reference, the comment above
schema_config.configs[*].store
says:However, when running loki with dynamodb as the client, the following message is sent to the logs:
To Reproduce
Steps to reproduce the behavior:
dynamodb
as per the documentation.Expected behavior
Starting up and using the dynamodb config was expected.
Environment:
Screenshots, Promtail config, or terminal output
The text was updated successfully, but these errors were encountered: