I'm assuming you're referring to Graylog Server "clustering" -- and not
MongoDB or ElasticSearch.
If "high availability" is important to you, then I'd suggest having at
least 2 Graylog Server processes running across as many availability zones
as possible (e.g. different racks in a data
Is anyone aware of a Kafka output plugin for Graylog 2.x? If not, is
Graylog itself considering creating/maintaining such a plugin in the near
future?
We're considering building one ourselves, but we'd like to ensure one
doesn't already exist (or in the works). We didn't find such a plugin
Would it make sense to increase the 'stale_master_timeout' setting to
something like 5 minutes? What would be the issues to consider with a
large cluster (say 32 Graylog Server nodes) having this set at 5 minutes
(instead of 2000ms)?
My understanding is that the master is only needed to run
Hi,
This appears to be more of an ElasticSearch question, rather than a
Graylog-specific question.
I'm going to guess that your ElasticSearch cluster doesn't have any
(primary) shards replicated to the other nodes in the cluster. When you
brought down one node, these shards were "lost" and
ed by Graylog, Inc. supports Graylog 2.x and later.
>
> Cheers,
> Jochen
>
> On Friday, 13 May 2016 19:11:10 UTC+2, Frederic Desjarlais wrote:
>>
>> Hi,
>>
>> With Graylog 2.0.0 (pre-GA), we've been using the Beats plugin from
>> https://github.com/sivasam
Hi,
With Graylog 2.0.0 (pre-GA), we've been using the Beats plugin
from https://github.com/sivasamyk/graylog-beats-plugin and we recently
noticed that Graylog now offers a Beats plugin
at https://github.com/Graylog2/graylog-plugin-beats .
Could someone describe the difference between these
We've been using Graylog 2.0.0 alpha-5 and now beta-1 -- hopefully my
response below is helpful to you.
To be clear, by "alpha" I'm assuming you mean the new Graylog 2.0 alpha
releases (e.g. alpha1, alpha2, ... , alpha5). There is now (as of today) a
"beta1" release of Graylog 2.0.
1)
