# Distributed Sensu setup?

**URL:** <https://discourse.sensu.io/t/distributed-sensu-setup/151>\
**Category:** Sensu Classic (EOL)\
**Created:** [March 4, 2014, 5:54pm UTC](https://discourse.sensu.io/t/distributed-sensu-setup/151 "2014-03-04T17:54:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joshua\_Zitting](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@Joshua\_Zitting](https://discourse.sensu.io/u/Joshua_Zitting)\
**Post date:** [March 4, 2014, 5:54pm UTC](https://discourse.sensu.io/t/distributed-sensu-setup/151/1 "2014-03-04T17:54:40Z")

</div>

Sorry to dig up old posts but it has been a year since this was answered and I was wondering if anything has changed… I have a similar need. We have equipment in 4 locations and I would like to monitor all with one sensu cluster…  
Is the best way still to set up some RabbitMQ shovelers at the remote sites and point them to the sensu cluster?

Thank you for any help in advance!

> **···**
>
> On Friday, March 22, 2013 6:08:48 AM UTC-6, Veselin Kantsev wrote:
> 
> > Hello,  
> > could you please direct me to any documentation on distributed Sensu setup?
> 
> > I’m operating two separate physical locations and would like to have
> 
> > a local Sensu server in each plus a 3rd one acting as a master/control node.
> 
> > 
> 
> > I’m unsure whether I need complete Sensu servers at both locations
> 
> > or just local message queues connecting back to the control node.
> 
> > 
> 
> > Regards,
> 
> > Veselin

---

<div class="post-metadata">

**Author:** ![Kyle\_Anderson](https://avatars.discourse-cdn.com/v4/letter/k/e5b9ba/32.png) [@Kyle\_Anderson](https://discourse.sensu.io/u/Kyle_Anderson)\
**Post date:** [March 5, 2014, 5:56am UTC](https://discourse.sensu.io/t/distributed-sensu-setup/151/2 "2014-03-05T05:56:28Z")

</div>

Depending on your latency and network requirements, you could either:

- Put all the sensu-servers in your “master” location, and co-locate your rabbitmq servers there, and have all clients phone-home there.

or

- Put your sensu-servers + rabbitmq on your “master” location, and then setup rabbitmq mirrors in your local pops and configure your sensu clients to use them.

I would not add additional complexity with master/slave relationships, just know what you are geting into:

[http://www.rabbitmq.com/ha.html](http://www.rabbitmq.com/ha.html)

What is best will be determined by you, and how your network is setup, latency conditions, etc.

> **···**
>
> On Tue, Mar 4, 2014 at 9:54 AM, Joshua Zitting [jzjoshzitting@gmail.com](mailto:jzjoshzitting@gmail.com) wrote:
> 
> > Sorry to dig up old posts but it has been a year since this was answered and I was wondering if anything has changed… I have a similar need. We have equipment in 4 locations and I would like to monitor all with one sensu cluster…  
> > Is the best way still to set up some RabbitMQ shovelers at the remote sites and point them to the sensu cluster?
> 
> > Thank you for any help in advance!
> 
> > On Friday, March 22, 2013 6:08:48 AM UTC-6, Veselin Kantsev wrote:
> > 
> > > Hello,  
> > > could you please direct me to any documentation on distributed Sensu setup?
> 
> > > I’m operating two separate physical locations and would like to have
> 
> > > a local Sensu server in each plus a 3rd one acting as a master/control node.
> 
> > >
> 
> > > I’m unsure whether I need complete Sensu servers at both locations
> 
> > > or just local message queues connecting back to the control node.
> 
> > >
> 
> > > Regards,
> 
> > > Veselin

---

<div class="post-metadata">

**Author:** ![Wyatt\_Walter](https://avatars.discourse-cdn.com/v4/letter/w/ed655f/32.png) [@Wyatt\_Walter](https://discourse.sensu.io/u/Wyatt_Walter)\
**Post date:** [March 5, 2014, 5:31pm UTC](https://discourse.sensu.io/t/distributed-sensu-setup/151/3 "2014-03-05T17:31:46Z")

</div>

This is how we are doing it, with federation instead of shovels.

We have central Sensu nodes which process events, with federated nodes in each pop. It works well for us so far… RabbitMQ management and orchestration seems to be the most painful part of using Sensu.

> **···**
>
> On Tuesday, March 4, 2014 11:54:40 AM UTC-6, Joshua Zitting wrote:
> 
> > Sorry to dig up old posts but it has been a year since this was answered and I was wondering if anything has changed… I have a similar need. We have equipment in 4 locations and I would like to monitor all with one sensu cluster…  
> > Is the best way still to set up some RabbitMQ shovelers at the remote sites and point them to the sensu cluster?
> 
> > Thank you for any help in advance!
> 
> > On Friday, March 22, 2013 6:08:48 AM UTC-6, Veselin Kantsev wrote:
> > 
> > > Hello,  
> > > could you please direct me to any documentation on distributed Sensu setup?
> 
> > > I’m operating two separate physical locations and would like to have
> 
> > > a local Sensu server in each plus a 3rd one acting as a master/control node.
> 
> > >
> 
> > > I’m unsure whether I need complete Sensu servers at both locations
> 
> > > or just local message queues connecting back to the control node.
> 
> > >
> 
> > > Regards,
> 
> > > Veselin

---

<div class="post-metadata">

**Author:** ![Greg\_Poirier](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@Greg\_Poirier](https://discourse.sensu.io/u/Greg_Poirier)\
**Post date:** [March 14, 2014, 3:30pm UTC](https://discourse.sensu.io/t/distributed-sensu-setup/151/4 "2014-03-14T15:30:33Z")

</div>

RabbitMQ is the part that most concerns me about my proposal for a federated Sensu. I’m currently thinking:

In each environment within each datacenter, I’ll have a separate Sensu server / RabbitMQ installation, then aggregate all of the results queues from these into queues for global metric storage and Sensu event aggregation in one or two datacenters.

> **···**
>
> On Wed, Mar 5, 2014 at 9:31 AM, Wyatt Walter [wwalter@sugarcrm.com](mailto:wwalter@sugarcrm.com) wrote:
> 
> > This is how we are doing it, with federation instead of shovels.
> 
> > We have central Sensu nodes which process events, with federated nodes in each pop. It works well for us so far… RabbitMQ management and orchestration seems to be the most painful part of using Sensu.
> 
> > 
> 
> > On Tuesday, March 4, 2014 11:54:40 AM UTC-6, Joshua Zitting wrote:
> > 
> > > Sorry to dig up old posts but it has been a year since this was answered and I was wondering if anything has changed… I have a similar need. We have equipment in 4 locations and I would like to monitor all with one sensu cluster…  
> > > Is the best way still to set up some RabbitMQ shovelers at the remote sites and point them to the sensu cluster?
> 
> > > Thank you for any help in advance!
> 
> > > On Friday, March 22, 2013 6:08:48 AM UTC-6, Veselin Kantsev wrote:
> > > 
> > > > Hello,  
> > > > could you please direct me to any documentation on distributed Sensu setup?
> 
> > > > I’m operating two separate physical locations and would like to have
> 
> > > > a local Sensu server in each plus a 3rd one acting as a master/control node.
> 
> > > >
> 
> > > > I’m unsure whether I need complete Sensu servers at both locations
> 
> > > > or just local message queues connecting back to the control node.
> 
> > > >
> 
> > > > Regards,
> 
> > > > Veselin

---

<div class="post-metadata">

**Author:** ![jspaleta](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/jspaleta/32/141_2.png) [@jspaleta](https://discourse.sensu.io/u/jspaleta)\
**Post date:** [November 22, 2018, 2:05am UTC](https://discourse.sensu.io/t/distributed-sensu-setup/151/5 "2018-11-22T02:05:08Z")

</div>