-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Combining Filesystem and S3 in Loki Schema Configuration #13949
Comments
hi this is my values.yaml
if i disable persistance, i keep getting following errors
|
@pen-pal, the initial question was about combining filesystem and S3 in the schema_config. Is it possible to use old logs from the filesystem while simultaneously storing new logs in S3? Currently, S3 works fine in my configuration without the filesystem setup, and the filesystem also works without the S3 setup. |
could you may be share me your values.yaml please for reference |
@vpotap can you share me your config so i can reference with s3 without using persistence? |
Questions have a better chance of being answered if you ask them on the community forums. |
Context: According to the Loki documentation, it seems possible to combine filesystem and s3 in the schema_config as shown in the example below:
Problem: I've tried multiple configurations based on the above setup, but after adding the S3 configuration, old logs stored in filesystem/boltdb-shipper are no longer visible in Grafana.
Question: Does this configuration work out of the box? Should I use a Python script or some other method to migrate the old logs from the filesystem to S3 first?
The text was updated successfully, but these errors were encountered: