-
Notifications
You must be signed in to change notification settings - Fork 1
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
Support multiple Ganeti clusters #5
Comments
i don't know if that's really necessary. installing the exporter once per cluster seems simple enough, and Prometheus will be happy to scrape multiple targets... one thing I've found in our deployments is that it really helps if the exporter can be installed on all nodes in the cluster, but only report metrics when it's running on the master. that way you don't need to implement business logic around "who is currently the master" in Prometheus and the deployment... That's how our current script works in ganeti/ganeti#47 (comment) |
Our scenario has multiple clusters and a single management node, which is able to reach all Master IPs directly. This could possibly also be solved with separate config files and some systemd magic (e.g. as it seen with openvpn on Debian which support multiple server configurations/processes). That would be a solution entirely outside of the exporter itself. In your scenario, what should the exporter exactly return when it is not running on the master? No metrics/values at all? Or the last seen value? |
On 2023-10-17 13:51:30, Rudolph Bott wrote:
In your scenario, what should the exporter exactly return when it is not running on the master? No metrics/values at all? Or the last seen value?
It returns nothing at all.
|
It would be nice if the exporter could query/export data from more than one Ganeti cluster.
The text was updated successfully, but these errors were encountered: