-
Notifications
You must be signed in to change notification settings - Fork 173
Support multiple APIs for the same data center #173
Comments
Wouldn't be easier to move the APIs behind a load balancer? I'm assuming that in case of an HA Sensu setup, a load balancer would already be in place for RabbitMQ, for example. |
Load balancers are still a single point of failure. @portertech implemented support for multiple RabbitMQ instances in 0.15.0.beta-1. If we decide to support this feature we can probably use Sensu's implementation as a reference. |
How I see it: we'll probably need to add an another property in the Sensu object of the JSON configuration file. Then, the URL property (which combine the Ssl, Host and Port properties) used by the backend would need to be replaced by a slice, in which we inject the single or multiple addresses (I'll assume that both APIs are configured with the same user/pass). Finally, whenever a call is made to the APIs, we iterate on the URL slice until we have a positive response. It's not impossible but it would definitively require a good amount of work! |
Guys, Hi. On a slightly different not, I would add distinction between GET and PUT/POST/DELETE API calls and let the administrator decide which API instance to query. It would help reading, for example, from an API connected to a local REDIS slave, and writing to a "master" on a different server. (i.e.: across the Atlantic perhaps) Regards, Andrei |
Added with 0.11.0 |
Wrong issue, my bad! |
Redundancy is a good thing. We should investigate implementing support for multiple APIs within the same data center so that Uchiwa can failover to another API & support rudimentary load balancing.
The text was updated successfully, but these errors were encountered: