New issue
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
Loki Does not Create Tables on DynamoDB #5070
Comments
You need to activate table_manager, the compactor is not compatible with NoSQL index. |
@cyriltovena Still not working and I have removed the compactor part and add table manager with 24 hours retention period and it did not work Configuration
Same error - Index not found
Also, please let me know what is the recommended DynamoDb Read/Write ratio for production and I am planning to store my logs for |
Do you have a pod that is running as the table-manager ? |
@cyriltovena Still not. For Prod, Are you recommend any suggestion |
I have found the same problem running the --target=all single binary deployment (not containerised). No sign of errors being logged, loki doesnt appear to even try to create the tables. |
Guys Any Updates on this |
The DynamoDB tables are created by the When starting the table manager, you should see log lines like these:
|
Could you give an example of your config. I use grafana/loki chart to run Loki and it also doesn't create a database, I tried to create a table manually but I don't understand where in the config I need to specify its name. |
"-target=all,table-manager" could be the solution as it did in my case. |
Yes, it helped me. I needed to add in default values extraArgs like extraArgs: Thanks! |
If anyone is still struggling with this one , on helm config add this code :
|
Loki Does not Create Tables on DynamoDB
I have configured Loki to Store chunks in s3 and indexes in DynamoDB. Each Day Loki looks for a Different table name and which is not created and therefore, it fails to show logs on my dashboard.
my index prefix is loki_index_
Loki looks for different index suffixes each day. Example loki_index_18997, loki_index_18998, loki_index_18999, etc
For the record, I used roles for my instance and it was given full access with loki_index_* resources
My Loki Configuration is as follows
**Error **
The text was updated successfully, but these errors were encountered: