# Graylog-server instances in a federated structure

**URL:** <https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516>\
**Category:** Graylog Central (peer support)\
**Created:** [March 20, 2017, 1:20pm UTC](https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516 "2017-03-20T13:20:05Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicozanf](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/nicozanf/32/33_2.png) [@nicozanf](https://community.graylog.org/u/nicozanf)\
**Post date:** [March 20, 2017, 1:20pm UTC](https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516/1 "2017-03-20T13:20:05Z")

</div>

Hello, I’ve read about it in the FAQ section of the 2.2 documentation - but it’s not so clear to me. Could someone kindly explain it a little more?

In my case, I have two sites and I’m thinking about installing two servers that receive everything (one on each site). Then, they forward only what I really need to a third _central_ one. Is there a way to automatically synchronize the configuration of the _front line_ servers?

Thank you,  
Nico

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [March 20, 2017, 2:18pm UTC](https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516/2 "2017-03-20T14:18:50Z")

</div>

> [@nicozanf](#):
>
> Is there a way to automatically synchronize the configuration of the front line servers?

You can use any configuration management solution, such as Puppet, Chef, or Ansible for this.

---

<div class="post-metadata">

**Author:** ![nicozanf](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/nicozanf/32/33_2.png) [@nicozanf](https://community.graylog.org/u/nicozanf)\
**Post date:** [March 21, 2017, 8:25pm UTC](https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516/3 "2017-03-21T20:25:39Z")

</div>

I see …

And what about the Graylog-server instances in a federated structure? Can you explain it?

Thank you

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [March 22, 2017, 8:40am UTC](https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516/4 "2017-03-22T08:40:34Z")

</div>

See [http://docs.graylog.org/en/2.2/pages/architecture.html#bigger-production-setup](http://docs.graylog.org/en/2.2/pages/architecture.html#bigger-production-setup) for a description of a load-balanced HA setup for Graylog.

How you’re going to implement that is completely up to you and your requirements.

---

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/david/32/226_2.png) [@david](https://community.graylog.org/u/david)\
**Post date:** [March 29, 2017, 5:56pm UTC](https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516/5 "2017-03-29T17:56:55Z")

</div>

Hello, I think I’m in the same case than @nicozanf.

Indeed, in this architecture (official documentation), each graylog server speak with the **same** elasticsearch cluster.

**My question is** : is it possible to have two or more **independant** graylog architecture (graylog + elasticsearch + mongodb) which are requested by another graylog server via https, sort of “master” role?

In fact, I will only use this Graylog server with “master” role more than a frontend to request other graylog server. There will be not connection with any elasticsearch cluster or mongodb replica set.

The reason is to save bandwidth. Because, some of them (sites on which I want install an indepedant graylog archtecure) only use vsat connection and the RTT is high (~300-600ms). So I don’t want impact them and avoid to lost some packets.

Thanks for your help! Graylog is a very nice and powerfull application! 🙂

David

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [March 29, 2017, 7:43pm UTC](https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516/6 "2017-03-29T19:43:17Z")

</div>

> [@david](#):
>
> is it possible to have two or more independant graylog architecture (graylog + elasticsearch + mongodb) which are requested by another graylog server via https, sort of “master” role?

No, that’s not possible.

---

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/david/32/226_2.png) [@david](https://community.graylog.org/u/david)\
**Post date:** [March 29, 2017, 8:27pm UTC](https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516/7 "2017-03-29T20:27:21Z")

</div>

Ok. Shorter is better…usually. Thanks.

---

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/david/32/226_2.png) [@david](https://community.graylog.org/u/david)\
**Post date:** [May 17, 2017, 8:32pm UTC](https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516/8 "2017-05-17T20:32:02Z")

</div>

Hello, I think the “Tribe” node could be a solution for us: [Tribe-node](https://www.elastic.co/blog/tribe-node)

From what I understand, the tribe node create a cluster that includes other clusters to be able to read in an almost transparent (depending the latency of network of course).

What do you think? It is compatible with Graylog?

David

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [May 18, 2017, 7:12am UTC](https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516/9 "2017-05-18T07:12:38Z")

</div>

> [@david](#):
>
> It is compatible with Graylog?

No, it’s not and it’s on the way out of Elasticsearch: [Tribe Nodes & Cross-Cluster Search: The Future of Federated Search in Elasticsearch | Elastic Blog](https://www.elastic.co/blog/tribe-nodes-and-cross-cluster-search-the-future-of-federated-search-in-elasticsearch)

---

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/david/32/226_2.png) [@david](https://community.graylog.org/u/david)\
**Post date:** [May 19, 2017, 2:16am UTC](https://community.graylog.org/t/graylog-server-instances-in-a-federated-structure/516/10 "2017-05-19T02:16:56Z")

</div>

I didn’t know this article, thank you for the link. Back to square one…
