-
Notifications
You must be signed in to change notification settings - Fork 486
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
[RFC] Multi-tenancy support in Flow #2583
base: main
Are you sure you want to change the base?
Conversation
3abc2f4
to
3583452
Compare
|
||
### Solution 2 - A generic "sharding" configuration for the Agent remote write | ||
|
||
The [```prometheus.remote_write```](https://grafana.com/docs/agent/latest/flow/reference/components/prometheus.remote_write/) Flow component could be expanded to be able to shard the writes into different remote writes under the hood. Each of these shards would have its own write-ahead log (WAL). Also, each shard would be able to remote write to a different endpoint address and with different HTTP header information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: Caching of series refs is per WAL, so if tenants have a lot of overlap with series, this can lead to ballooning memory usage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, thank you, I added this to the "cons" list. Although not sure if it's a "con" it's more like just something to keep in mind.
There is also https://github.com/blind-oracle/cortex-tenant which seems to fit the needs? |
dca20fa
to
f79d69d
Compare
Of course! How could I forget 😆 Thanks for reminding me, I added that too. |
Proposes several approaches to support (or not) multi-tenancy within Flow. Solves grafana/alloy#521.