-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Thanos receive per tenant limits #3819
Comments
cc @spaparaju |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Still valid. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Is this completed with #5685 and others? |
Do we have or do we want to have all these limits on the ingestion path? |
Is your proposal related to a problem?
If writing untrusted data to a Thanos receive cluster, you want to be able to limit the damage that can be done.
Describe the solution you'd like
Allow configuring per tenant limits for:
Describe alternatives you've considered
Doing this outside of Thanos, or not using Thanos. Doing this outside of Thanos wouldn't allow limiting active series though, which is argulably the biggest factor of memory used by Thanos receive.
@thanos-io/thanos-maintainers
The text was updated successfully, but these errors were encountered: