I attached an an example of some of the behavior I observe. This is
sporadic, and switches between one node at a time to all of the nodes for
extended periods. However, the log reception is at a normal capacity.
On Monday, January 16, 2017 at 9:59:19 AM UTC-7, Zach Stoddard wrote:
>
>
Hi Stefano,
On Monday, 16 January 2017 17:36:38 UTC+1, Stefano Tranquillini wrote:
>
> - what happens if i rename the cluster.name from 'graylog' to something
> else?
>
Graylog will simply connect to the given Elasticsearch cluster. It will not
automatically copy indices from the old cluster.
Struggling to maintain a web cluster behind a AWS Class load balancer.
I manage to get the cluster master set up and working behind the Load
balancer (UI), and the Elasticsearch storage cluster works great.
Trying to add additional web servers to cluster, has funny behavior.
When the REST API
Thanks,
so my strategy is to rename put them in the same cluster, and have replica
1. so that the indices are spread to both VMs and once everything is green
i can switch one of.
Now:
- is there a better strategy?
- what happens if i rename the cluster.name from 'graylog' to something
else?
On
Hi Stefano,
On Monday, 16 January 2017 16:20:35 UTC+1, Stefano Tranquillini wrote:
>
> Now, how bad is the idea to have just 1 elasticsearch (so stop the one in
> A and keep the one in B) for graylog and our searches? Is that a problem?
>
If your Elasticsearch cluster can handle the load of
Hi all,
Question: i've a server with several VMs and one contains elastic+graylog
etc (let's call it A), then I've a second VM where there's another istance
of elasticsearch used for other means (we do index documents for searches
there) (let's call B).
Now, how bad is the idea to have just 1
Jochen,
The uri http://:12900/ worked.
Thanks!
On Monday, January 16, 2017 at 4:25:44 AM UTC-5, Jochen Schalanda wrote:
>
> Hi Scott,
>
> without knowing your Graylog configuration, the URI
> http://:12900/api/ looks wrong. It should probably be either
> http://:12900/ or http://:9000/api/,
Hi,
please refer
to
http://docs.graylog.org/en/2.1/pages/installation/virtual_machine_appliances.html
and http://docs.graylog.org/en/2.1/pages/configuration/graylog_ctl.html for
details about the virtual machine images.
Cheers,
Jochen
On Monday, 16 January 2017 11:11:30 UTC+1, Hyder wrote:
Hello,
I've downloaded and imported the supplied OVA image that is available
here..
http://docs.graylog.org/en/2.1/pages/installation/virtual_machine_appliances.html
What is the setup in the supplied Graylog OVA? (how many Elastic Search
nodes, Mongodb instances etc.?
Regards,
Hyder
--
On Mon, Jan 16, 2017 at 10:24 PM, Jochen Schalanda
wrote:
> please stick to the format explained in http://docs.graylog.org/en/
> 2.1/pages/configuration/multinode_setup.html#graylog-to-mongodb-connection
> and https://github.com/Graylog2/graylog2-server/blob/
>
Hi,
how did you configure Graylog?
By default, the Graylog REST API and the web interface will only to
localhost (127.0.0.1).
Cheers,
Jochen
On Sunday, 15 January 2017 02:31:40 UTC+1, JayJay wrote:
>
> Hi,
> I just installed latest on CentOS7, and can open the web console on
>
Hi Scott,
without knowing your Graylog configuration, the URI
http://:12900/api/ looks wrong. It should probably be either
http://:12900/ or http://:9000/api/, depending on
your Graylog configuration.
Cheers,
Jochen
On Sunday, 15 January 2017 16:42:38 UTC+1, Scott LeFevre wrote:
>
> I've
Hi Jason,
please stick to the format explained
in
http://docs.graylog.org/en/2.1/pages/configuration/multinode_setup.html#graylog-to-mongodb-connection
and
https://github.com/Graylog2/graylog2-server/blob/2.1.2/misc/graylog.conf#L434-L442
for the mongodb_uri setting.
Also see the error
13 matches
Mail list logo