Skip to content
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

Adopt for bare-metal setups #85

Open
GiedriusS opened this issue Jan 3, 2022 · 2 comments
Open

Adopt for bare-metal setups #85

GiedriusS opened this issue Jan 3, 2022 · 2 comments

Comments

@GiedriusS
Copy link

Hello! Thank you for your project. I was thinking about how much effort it would be to make this suitable for bare-metal setups as well. Essentially, it should perform all of the same things except for the automation of scaling down/up. The goal is to have an equal load over all Prometheus instances. Do you think this would make sense for your project? If yes maybe I could contribute.

@RayHuangCN
Copy link
Member

Hi 😊 , thank you for your advice! We already support a simple static shards way for bare-metal now.
User can provide a shards config for Coordinator to indicate shards information.

  • add --shard.type=static and --shard.static-file=xxx.yaml for Coordinator
  • add --config.file="" for Sidecar to get config file from Coordiantor (no local config file needed)

but this feature is kind of weak now

  • shards can only use the same max series
  • scaling down/up event is unavailable.

I think that we can support http way, which use a shards server for fetch shards information, and deal with scaling down/up event.

@GiedriusS
Copy link
Author

I see. I'll try it out and come back with any comments/suggestions. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants