Re: [graylog2] Graylog slow processing.

2016-07-14 Thread Hema Kumar
buffer is full but the journal holds nearly 150,000,000 messages. I am left with no options, any suggestions would be great. Thanks, Hema. On Monday, July 11, 2016 at 1:27:46 PM UTC+5:30, Jan Doberstein wrote: > > Hey Hema, > > > On 8. Juli 2016 at 14:10:50, Hema Kumar (v

[graylog2] Re: Graylog slow processing.

2016-07-11 Thread Hema Kumar
range, i did the "Recalculate index cycles" which fixed that, but the slow processing has accumulated about 100,000,000 messages in the journal on the Master Node. Still finding what is happening.. :-( Thanks Hema. On Friday, July 8, 2016 at 5:40:47 PM UTC+5:30, Hema Kumar wro

[graylog2] Graylog slow processing.

2016-07-08 Thread Hema Kumar
Hi, I am using graylog 1.3.3 with ES 1.7.5, from yesterday we are seeing the process buffer filled up on the master node and the outgoing process is too slow than normal, I have tried restarting GL and ES but did not fix the issue, below are the log warn and errors we see that repeats continu

[graylog2] Get number of sources and source names using API

2016-03-14 Thread Hema Kumar
Hi, - Is there an API to list the hostnames (Sources) and the total number of hosts in graylog. - Also is there an API to list the number of messages received per host/source for a day. Thanks, Hema. -- You received this message because you are subscribed to the Google Groups "Graylog User

[graylog2] Increase the number of items the displays in Quick values in the widget

2016-01-07 Thread Hema Kumar
Hi, When we use the Quick values in the widget, it displays only about 50 items in the value the rest of the details are not shown, when the search query is changed ignoring few patterns of the current values, we get to see the rest of the missing items. https://github.com/Graylog2/graylog2-

[graylog2] Capacity Requirement

2015-06-18 Thread Hema Kumar
Hi, Our environment is setup as such, 2 graylog servers with 4 Cpu and 8 GB Ram / node, where the allocated heap is 4GB/node 3 Elasticsearch servers with 8 Cpu and 30 GB Ram / node, where the allocated heap is 20 GB / Node. 1 mongodb and graylog web server with 2 cpu and 4 GB Ram. Our polic

[graylog2] Re: Log Rotation

2015-04-16 Thread Hema Kumar
tenance -> > Recalculate index ranges). > > Cheers, > Jochen > > On Tuesday, 7 April 2015 13:51:28 UTC+2, Hema Kumar wrote: >> >> Hi Jochen, >> If i build a shell script using the API and move the closed indice >> files to different location, woul

[graylog2] Re: Log Rotation

2015-04-07 Thread Hema Kumar
create a snapshot of them). Maybe you could even use Curator ( > http://www.elastic.co/guide/en/elasticsearch/client/curator/current/about.html) > > for that. > > Cheers, > Jochen > > On Friday, 3 April 2015 01:35:00 UTC+2, Hema Kumar wrote: >> >> Hi, >&

[graylog2] Log Rotation

2015-04-02 Thread Hema Kumar
Hi, Is there a way to do a log Rotation - My policy is to hold 60 days of indices which was done in the configs, the logs more than 60 days are closed. - The second thing is after 60 days the closed indices should be moved to different drive and should hold it for 120 days but should still be