[graylog2] Re: Can't delete an input in Graylog 2.0 Beta.3

Hi Jayica, would you mind telling us what the problem was? Maybe we can improve something in the documentation or in the code of Graylog. Cheers, Jochen On Friday, 22 April 2016 19:34:27 UTC+2, Jayica wrote: > > Thanks Jochen. This was all very helpful. Problem solved. > > On Sunday, April

[graylog2] Sending only Errors and warning from the log files using Collector

Hello Team, I am currently using a Graylog Collector v0.4.2 , to send application logs to my Graylog sever (1.3.4 (0d67a80) (*Hansa*)). I just wanted to know is it possible to send only the Errors and warnings level from the application logs to the Graylog server using the collector. My

[graylog2] Re: Can't delete an input in Graylog 2.0 Beta.3

Thanks Jochen. This was all very helpful. Problem solved. On Sunday, April 17, 2016 at 7:04:36 PM UTC-4, Jayica wrote: > > I just installed Graylog 2.0.0-beta.3 and created an input (which was > working fine until I added an elastic IP to my Graylog AWS instance - while > it was up and

[graylog2] Re: Output rate very low with graylog 2.0rc1

I have only one GELF input on each node and no extractors. I forgot to mention that logstash is also running on each node, it receives all the message, does some filtering then sends the messages to graylog via gelf. I've just disabled all the logstash filters but still have the performance

[graylog2] Re: Output rate very low with graylog 2.0rc1

Hi, what kind of inputs are you running and are you using any extractors or the message processing pipeline? A full process buffer usually hints to slow/complex message filtering or extractors. Cheers, Jochen On Friday, 22 April 2016 16:29:41 UTC+2, oliv@gmail.com wrote: > > Hi, > I have

[graylog2] Output rate very low with graylog 2.0rc1

Hi, I have a problem with my output rate which is very low. My input rate is not very high (200-400 msg/sec) but the output gets stuck at 100msg/sec max. As you can see in the following screenshot, the process and output buffers are at 100% and the journal is pretty full. [image: graylog]

[graylog2] Re: Can't delete an input in Graylog 2.0 Beta.3

Hi Jayica, did you change the Node ID of the Graylog node (e. g. replaced the node-id-file )? Does the input still exist (is it shown in the web interface on the System -> Inputs page)? You can always just

Re: [graylog2] Re: Permission to see the log

Thank you Jochen have a nice day. 2016-04-22 10:42 GMT+03:00 Jochen Schalanda : > Hi Hasan, > > you're thinking right, streams for the different groups are the way to go. > If you have a specific field for the Apache httpd access logs, you can > simply check for that field

[graylog2] Re: Can't delete an input in Graylog 2.0 Beta.3

Well that's just it, my URL has changed to a new address (defined under rest_transport_uri) so all i want to do is delete my old input (which was pointing to the old URL) and create a new one. Graylog is not letting me delete my old input though because of this. There's got to be some way to

Re: [graylog2] Searching broke, no idea what to do (dashboard still works)

The data in there looks fine to me, I could even load some empty charts with it. Did removing the data from the localStorage help with the search problem? >From the output you posted, I think you are still missing to do >`localStorage.removeItem('pinned-field-charts')`. By the way, we still

[graylog2] Re: HA setup with redundant paths: avoid duplicates

This is a good question. Redundant log entries are a problem for us as well. I'm looking for a way to get rid of them. I hope someone answers... On Tuesday, March 15, 2016 at 11:32:20 AM UTC-4, tok...@gmx.net wrote: > > Hi! > > We are currently planning a large scale Graylog setup,

[graylog2] Re: fielddata error with search

Hi Yes, that's a bummer unfortunately. Anyway i find it a bit weird that `message` field is taking up so much space to trigger a breaker. It's not even in the query so why it gets loaded? When i was monitoring my fielddata and switching to doc_values in my setup other smaller fields were my

[graylog2] Re: Permission to see the log

Hi Hasan, you're thinking right, streams for the different groups are the way to go. If you have a specific field for the Apache httpd access logs, you can simply check for that field in the stream rules. Cheers, Jochen On Thursday, 21 April 2016 22:54:44 UTC+2, hasan akgöz wrote: > > Hi