-
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
allow to configure s3 subpath (bucket prefix configuration) #5889
Comments
I think this issue is very important and I am facing the same problem. |
Facing the same problem. This is very much needed since we are using that bucket for other purposes as well. Making it into a subpath will make it much neater. |
Need the same feature here, so that I can fit all the observability backends in the same bucket (thanos, loki...)! |
Hi! This issue has been automatically marked as stale because it has not had any We use a stalebot among other tools to help manage the state of issues in this project. Stalebots are also emotionless and cruel and can close issues which are still very relevant. If this issue is important to you, please add a comment to keep it open. More importantly, please add a thumbs-up to the original issue entry. We regularly sort for closed issues which have a We may also:
We are doing our best to respond, organize, and prioritize all issues but it can be a challenging task, |
Bumping it cause we are having the same problem. |
Loki communicates with the S3 bucket using the Since thanos-io/thanos#5337 has been merged, implementing bucket prefix in loki should be much simpler. |
@dimitarvdimitrov - thank you for grafana/mimir#1686 was wondering if there are any plans to retrofit this into loki as well? Thank you. |
Is there any update on this? |
+1000 on this one! Really important when you want to backup a complete |
Is there any update on this one? |
Any updates? Really need this feature to keep it align with mimir and tempo! |
I currently set up one loki per k8s cluster (via the helm chart) and this would be handy to allow all my clusters in a given environment (dev, prod, etc) to have a common log storage bucket rather than For now I'll just live with the dozen or so extra buckets produced by the above multiplication. |
**What this PR does / why we need it**: Adds a new option under the aws stanza named key_prefix. This is useful if you have many Loki installations and do not want to create a million buckets. This is different than `compactor.shared_store_key_prefix` because it also affects eg the `loki_cluster_seed.json` file. **Which issue(s) this PR fixes**: Fixes #5889 **Special notes for your reviewer**: **Checklist** - [x] Reviewed the [`CONTRIBUTING.md`](https://github.com/grafana/loki/blob/main/CONTRIBUTING.md) guide (**required**) - [x] Documentation added - [x] Tests updated - [x] `CHANGELOG.md` updated - [ ] If the change is worth mentioning in the release notes, add `add-to-release-notes` label - [x] Changes that require user attention or interaction to upgrade are documented in `docs/sources/setup/upgrade/_index.md` - [ ] For Helm chart changes bump the Helm chart version in `production/helm/loki/Chart.yaml` and update `production/helm/loki/CHANGELOG.md` and `production/helm/loki/README.md`. [Example PR](d10549e) --------- Signed-off-by: Edward Welch <[email protected]> Co-authored-by: Ed Welch <[email protected]>
Is there any update on this one? |
Also interested in how this is done for the helm chart. Is it documented somewhere? |
Is there any update on this one? |
Hi, I'm a bit lost, I want to use this feature that should be available since #10096 got merged (it's in the code) but with loki
I set A quick search of the issues show that people use this feature, but how can it work if it's not accepted by storage.Config ? EDIT: goddammit there is a |
On that note, this feature has now been merged to main for nearly 5 whole months but not included in 2.9.3, 2.9.4, or 2.9.5. Could this please get included in a release, and also updated in the helm chart, added to documentation, etc? @slim-bean I see you're the one who merged the original feature, so I'm tagging you for visibility |
…a#10096) **What this PR does / why we need it**: Adds a new option under the aws stanza named key_prefix. This is useful if you have many Loki installations and do not want to create a million buckets. This is different than `compactor.shared_store_key_prefix` because it also affects eg the `loki_cluster_seed.json` file. **Which issue(s) this PR fixes**: Fixes grafana#5889 **Special notes for your reviewer**: **Checklist** - [x] Reviewed the [`CONTRIBUTING.md`](https://github.com/grafana/loki/blob/main/CONTRIBUTING.md) guide (**required**) - [x] Documentation added - [x] Tests updated - [x] `CHANGELOG.md` updated - [ ] If the change is worth mentioning in the release notes, add `add-to-release-notes` label - [x] Changes that require user attention or interaction to upgrade are documented in `docs/sources/setup/upgrade/_index.md` - [ ] For Helm chart changes bump the Helm chart version in `production/helm/loki/Chart.yaml` and update `production/helm/loki/CHANGELOG.md` and `production/helm/loki/README.md`. [Example PR](grafana@d10549e) --------- Signed-off-by: Edward Welch <[email protected]> Co-authored-by: Ed Welch <[email protected]>
Is your feature request related to a problem? Please describe.
Currently a full S3 bucket is required for Loki - however, in some situations a bucket may need to be shared with other apps (one example would be aws lightsail where there's a fixed cost per bucket).
Describe the solution you'd like
Ability to specify a folder where all Loki data will be stored in a bucket
I've raised a similar issue with Mimir: grafana/mimir#1682
Thank you.
The text was updated successfully, but these errors were encountered: