Hi all,
I’d like to know the requirements for setting up multiple Sensu instances such that they behave as their own datacenters. When setting up Uchiwa, it appears that in the configuration, you point to a distinct Sensu API per datacenter. Does this mean I only need to spin up a Sensu API instance per datacenter, or do I need the whole deployment (distinct server, api, RabbitMQ, Redis)?
What I’m really trying to avoid is having to spin up multiple instances of RabbitMQ and Redis; I’d like to share them between datacenters if possible.
Thanks!
Sensu does not have the concept of a datacenter you can have multiple distinct sensu setups and connect them all to a single uchiwa which does have the concept of datacenters. You can of course do one uchiwa per data center or even mix and match to have each sensu have its own uchiwa but then have a meta uchiwa that includes all environments.
···
On Wednesday, February 14, 2018 at 3:46:32 PM UTC-8, Chris Zacny wrote:
Hi all,
I’d like to know the requirements for setting up multiple Sensu instances such that they behave as their own datacenters. When setting up Uchiwa, it appears that in the configuration, you point to a distinct Sensu API per datacenter. Does this mean I only need to spin up a Sensu API instance per datacenter, or do I need the whole deployment (distinct server, api, RabbitMQ, Redis)?
What I’m really trying to avoid is having to spin up multiple instances of RabbitMQ and Redis; I’d like to share them between datacenters if possible.
Thanks!