Re: [graylog2] Graylog 1.0 UDP process buffer performance
Thanks for the feedback! :) Bernd On 2 March 2015 at 11:26, sun...@sunner.com wrote: I installed unbound locally and used this, and it seems to have resolved the issue. It's odd that the old server didn't show this behavior, but I'm happy enough that it's resolved anyway. :) Regards Johan On Friday, February 27, 2015 at 2:02:08 PM UTC+1, Bernd Ahlers wrote: Johan, Henrik, I tried to track this problem down.The problem is that the JVM does not cache reverse DNS lookups. The available JVM DNS cache settings like networkaddress.cache.ttl only affect forward DNS lookups. The code for doing the reverse lookups in Graylog did not change in a long time, so this problem is not new in 1.0. I my test setup enabling force_rdns for a syslog input reduced the throughput from around 7000 msg/s to 300 msg/s. This was without a local DNS cache. Once I installed a DNS cache on the Graylog server, the throughput went up to around 3000 msg/s. We will investigate if there is a sane way to cache the reverse lookups ourselves. In the meantime I suggest to test with a DNS cache installed on the Graylog server nodes to see if that helps or to disable the force_rdns setting. Regards, Bernd On 25 February 2015 at 18:00, Bernd Ahlers be...@graylog.com wrote: Johan, Henrik, thanks for the details. I created an issue on GitHub and will investigate. https://github.com/Graylog2/graylog2-server/issues/999 Regards, Bernd On 25 February 2015 at 17:48, Henrik Johansen h...@myunix.dk wrote: Bernd, Correct - that issue started after 0.92.x. We are still seeing evaluated CPU utilisation but we are attributing that to the fact that 0.92 was loosing messages in our setup. On 25 Feb 2015, at 17:37, Bernd Ahlers be...@graylog.com wrote: Henrik, uh, okay. I suppose it worked for you in 0.92 as well? I will create an issue on GitHub for that. Bernd On 25 February 2015 at 17:14, Henrik Johansen h...@myunix.dk wrote: Bernd, We saw the exact same issue - here is a graph over the CPU idle percentage across a few of the cluster nodes during the upgrade : http://5.9.37.177/graylog_cluster_cpu_idle.png We went from ~20% CPU utilisation to ~100% CPU utilisation across ~200 cores and things only settled down after disabling force_rdns. On 25 Feb 2015, at 11:55, Bernd Ahlers be...@graylog.com wrote: Johan, the only thing that changed from 0.92 to 1.0 is that the DNS lookup is now done when the messages are read from the journal and not in the input path where the messages are received. Otherwise, nothing has changed in that regard. We do not do any manual caching of the DNS lookups, but the JVM caches them by default. Check http://docs.oracle.com/javase/7/docs/technotes/guides/net/properties.html for networkaddress.cache.ttl and networkaddress.cache.negative.ttl. Regards, Bernd On 25 February 2015 at 08:56, sun...@sunner.com wrote: This is strange, I went through all of the settings for my reply, and we are indeed using rdns, and it seems to be the culprit. The strangeness is that it works fine on the old servers even though they're on the same networks, and using the same DNS's and resolver settings. Did something regarding reverse DNS change between 0.92 and 1.0? I'm thinking perhaps the server is trying to do one lookup per message instead of caching reverse lookups, seeing as the latter would result in very little DNS traffic since most of the logs will be coming from a small number of hosts. Regards Johan On Tuesday, February 24, 2015 at 5:08:54 PM UTC+1, Bernd Ahlers wrote: Johan, this sounds very strange indeed. Can you provide us with some more details? - What kind of messages are you pouring into Graylog via UDP? (GELF, raw, syslog?) - Do you have any extractors or grok filters running for the messages coming in via UDP? - Any other differences between the TCP and UDP messages? - Can you show us your input configuration? - Are you using reverse DNS lookups? Thank you! Regards, Bernd On 24 February 2015 at 16:45, sun...@sunner.com wrote: Well that could be a suspect if it wasn't for the fact that the old nodes running on old hardware handle it just fine, along with the fact that the traffic seems to reach the nodes just fine(i.e it actually fills the journal up just fine, and the input buffer never breaks a sweat). And it's really not that much traffic, even spread across four nodes those ~1000 messages per second will cause this whereas the old nodes are just two and can handle it just fine. About disk tuning, I haven't done much of that, and I realize I forgot to mention that the Elasticsearch cluster is on separate physical hardware so there's a minuscule amount of disk I/O happening on the Graylog nodes. It's really very strange since it seems like UDP
[graylog2] Message stay in disk journal and are not sent to elasticsearch
Hi Everybody,
I have an issue with the graylog 1.0.
Inputs receive messages but they stay in disk journal and are not send to
elasticsearch (the disk jounal is growing and node processing is enabled
...).
The elasticsearch cluster is green, the deflector is pointing to the good
indice (graylog2_55) but there is 0 messages in it.
I tried to add a message manually in the graylog2_55 indice with success (
curl -XPOST 'http://127.0.0.1:9200/graylog2_55/messages/' -d '{ user:
test }' ).
Can i have more logs to know why graylog is not sending logs to
elasticsearch ?
Thank you.
Benjamin.
--
You received this message because you are subscribed to the Google Groups
graylog2 group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[graylog2] Cloudtrail - consuming responseElements object
Hi, I'm evaluating Cloud trail plugin for graylog2. Everything is working fine, but it seems that is not importing responseElements cloudtrail object. Is this the case? How can I add to import this? That's essential for an auditing solution, as at the moment, if I filter by event_name=ConsoleLogin for example, I can't track failed authentication. The same thing for most of the events. Prob the requestElements could also be handy in some cases... -- Rubicon Red wins 3 Oracle Excellence Awards for Fusion Middleware http://www.rubiconred.com/rubicon-red-wins-3-oracle-excellence-awards-fusion-middleware/ http://www.rubiconred.com Rubicon Red Privacy Policy http://www.rubiconred.com/privacy-policy-2/ -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] You caused a org.graylog2.restclient.lib.APIException. API call failed GET after upgrade to 1.0.0
After upgrading my graylog cluster from .92 to 1.0.0 clustered setup the system tab is no longer accessible. The test upgrade I did went flawlessly so not sure what the deal is. *You caused a org.graylog2.restclient.lib.APIException. API call failed GET **Reason:* Could not fetch system information. We expected HTTP 200, but got a HTTP -1. - org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder#execute ( *ApiClientImpl.java:498*) - org.graylog2.restclient.models.ClusterService#getNumberOfSystemMessages (*ClusterService.java:128*) - controllers.SystemController#index (*SystemController.java:65*) - Routes$$anonfun$routes$1$$anonfun$applyOrElse$43$$anonfun$apply$491#apply (*routes_routing.scala:1669*) - Routes$$anonfun$routes$1$$anonfun$applyOrElse$43$$anonfun$apply$491#apply (*routes_routing.scala:1669*) - play.core.Router$HandlerInvokerFactory$$anon$4#resultCall ( *Router.scala:264*) - play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1#invocation (*Router.scala:255*) - play.core.j.JavaAction$$anon$1#call (*JavaAction.scala:55*) - play.GlobalSettings$1#call (*GlobalSettings.java:67*) - play.mvc.Security$AuthenticatedAction#call (*Security.java:44*) - play.core.j.JavaAction$$anonfun$11#apply (*JavaAction.scala:82*) - play.core.j.JavaAction$$anonfun$11#apply (*JavaAction.scala:82*) - scala.concurrent.impl.Future$PromiseCompletingRunnable#liftedTree1$1 ( *Future.scala:24*) - scala.concurrent.impl.Future$PromiseCompletingRunnable#run ( *Future.scala:24*) - play.core.j.HttpExecutionContext$$anon$2#run ( *HttpExecutionContext.scala:40*) - play.api.libs.iteratee.Execution$trampoline$#execute ( *Execution.scala:46*) - play.core.j.HttpExecutionContext#execute ( *HttpExecutionContext.scala:32*) - scala.concurrent.impl.Future$#apply (*Future.scala:31*) - scala.concurrent.Future$#apply (*Future.scala:485*) - play.core.j.JavaAction$class#apply (*JavaAction.scala:82*) - play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1#apply (*Router.scala:252*) - play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5#apply (*Action.scala:130*) - play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5#apply (*Action.scala:130*) - play.utils.Threads$#withContextClassLoader (*Threads.scala:21*) - play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4#apply ( *Action.scala:129*) - play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4#apply ( *Action.scala:128*) - scala.Option#map (*Option.scala:145*) - play.api.mvc.Action$$anonfun$apply$1#apply (*Action.scala:128*) - play.api.mvc.Action$$anonfun$apply$1#apply (*Action.scala:121*) - play.api.libs.iteratee.Iteratee$$anonfun$mapM$1#apply ( *Iteratee.scala:483*) - play.api.libs.iteratee.Iteratee$$anonfun$mapM$1#apply ( *Iteratee.scala:483*) - play.api.libs.iteratee.Iteratee$$anonfun$flatMapM$1#apply ( *Iteratee.scala:519*) - play.api.libs.iteratee.Iteratee$$anonfun$flatMapM$1#apply ( *Iteratee.scala:519*) - play.api.libs.iteratee.Iteratee$$anonfun$flatMap$1$$anonfun$apply$14#apply (*Iteratee.scala:496*) - play.api.libs.iteratee.Iteratee$$anonfun$flatMap$1$$anonfun$apply$14#apply (*Iteratee.scala:496*) - scala.concurrent.impl.Future$PromiseCompletingRunnable#liftedTree1$1 ( *Future.scala:24*) - scala.concurrent.impl.Future$PromiseCompletingRunnable#run ( *Future.scala:24*) - akka.dispatch.TaskInvocation#run (*AbstractDispatcher.scala:41*) - akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask#exec ( *AbstractDispatcher.scala:393*) - scala.concurrent.forkjoin.ForkJoinTask#doExec (*ForkJoinTask.java:260*) - scala.concurrent.forkjoin.ForkJoinPool$WorkQueue#runTask ( *ForkJoinPool.java:1339*) - scala.concurrent.forkjoin.ForkJoinPool#runWorker ( *ForkJoinPool.java:1979*) - scala.concurrent.forkjoin.ForkJoinWorkerThread#run ( *ForkJoinWorkerThread.java:107*) -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] Message stay in disk journal and are not sent to elasticsearch
Hi Benjamin,
You can enable the debug logs passing --debug to the server command. If you
upgraded from an old Graylog version, please also double check the contents of
your Graylog server configuration file.
Regards,
Edmundo
--
Developer
Tel.: +49 (0)40 609 452 077
Fax.: +49 (0)40 609 452 078
TORCH GmbH - A Graylog company
Steckelhörn 11
20457 Hamburg
Germany
Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175
Geschäftsführer: Lennart Koopmann (CEO)
On 02 Mar 2015, at 15:18, Benjamin CALLAR knasucr...@gmail.com wrote:
Hi Everybody,
I have an issue with the graylog 1.0.
Inputs receive messages but they stay in disk journal and are not send to
elasticsearch (the disk jounal is growing and node processing is enabled
...).
The elasticsearch cluster is green, the deflector is pointing to the good
indice (graylog2_55) but there is 0 messages in it.
I tried to add a message manually in the graylog2_55 indice with success (
curl -XPOST 'http://127.0.0.1:9200/graylog2_55/messages/' -d '{ user: test
}' ).
Can i have more logs to know why graylog is not sending logs to elasticsearch
?
Thank you.
Benjamin.
--
You received this message because you are subscribed to the Google Groups
graylog2 group.
To unsubscribe from this group and stop receiving emails from it, send an
email to graylog2+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
graylog2 group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Alert condition if field message contains string or matches regex
Hi everybody I still trying to create alerts on stream when a field contains string or matches a regex. Have you any idea of how to do that without creating a new stream for each alert ? Thanks in advance Regards Yves Louis Le jeudi 22 janvier 2015 10:56:57 UTC+1, yvesloui...@gmail.com a écrit : Hi Jochen, Thanks for your advice, I tried this morning the beta3 (graylog-server with graylog-web) with same mogo database (created with an older version). Should I recreate a new mongo database ? I still don't find how to use regex in alert rules Regards Yves Louis Le jeudi 22 janvier 2015 10:33:15 UTC+1, Jochen Schalanda a écrit : Hi Yves, On Wednesday, 21 January 2015 08:48:40 UTC+1, yvesloui...@gmail.com wrote: I tried with graylog2-web 0.92.4 and this morning with graylog2-web-interface-1.1.0-SNAPSHOT-20150115173058, without success. FWIW, the Graylog web interface usually just works with the matching version of the server. So if you've tried graylog2-web-interface 1.1.0-SNAPSHOT with graylog2-server 0.92.4, that most probably didn't work because they're incompatible. Cheers, Jochen -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] Alert condition if field message contains string or matches regex
Hi, There already is an existing feature request for this : https://github.com/Graylog2/graylog2-server/issues/537 https://github.com/Graylog2/graylog2-server/issues/537 Implementation is currently scheduled for the 1.1.0 release ... On 03 Mar 2015, at 10:52, yveslouis.rof...@gmail.com wrote: Hi everybody I still trying to create alerts on stream when a field contains string or matches a regex. Have you any idea of how to do that without creating a new stream for each alert ? Thanks in advance Regards Yves Louis Le jeudi 22 janvier 2015 10:56:57 UTC+1, yvesloui...@gmail.com a écrit : Hi Jochen, Thanks for your advice, I tried this morning the beta3 (graylog-server with graylog-web) with same mogo database (created with an older version). Should I recreate a new mongo database ? I still don't find how to use regex in alert rules Regards Yves Louis Le jeudi 22 janvier 2015 10:33:15 UTC+1, Jochen Schalanda a écrit : Hi Yves, On Wednesday, 21 January 2015 08:48:40 UTC+1, yvesloui...@gmail.com wrote: I tried with graylog2-web 0.92.4 and this morning with graylog2-web-interface-1.1.0-SNAPSHOT-20150115173058, without success. FWIW, the Graylog web interface usually just works with the matching version of the server. So if you've tried graylog2-web-interface 1.1.0-SNAPSHOT with graylog2-server 0.92.4, that most probably didn't work because they're incompatible. Cheers, Jochen -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com mailto:graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] Alert condition if field message contains string or matches regex
Hi Henrik Thanks, I haven't found this issue. Regards Yves Louis ROFORT Le mardi 3 mars 2015 11:06:43 UTC+1, Henrik Johansen a écrit : Hi, There already is an existing feature request for this : https://github.com/Graylog2/graylog2-server/issues/537 Implementation is currently scheduled for the 1.1.0 release ... On 03 Mar 2015, at 10:52, yvesloui...@gmail.com javascript: wrote: Hi everybody I still trying to create alerts on stream when a field contains string or matches a regex. Have you any idea of how to do that without creating a new stream for each alert ? Thanks in advance Regards Yves Louis Le jeudi 22 janvier 2015 10:56:57 UTC+1, yvesloui...@gmail.com a écrit : Hi Jochen, Thanks for your advice, I tried this morning the beta3 (graylog-server with graylog-web) with same mogo database (created with an older version). Should I recreate a new mongo database ? I still don't find how to use regex in alert rules Regards Yves Louis Le jeudi 22 janvier 2015 10:33:15 UTC+1, Jochen Schalanda a écrit : Hi Yves, On Wednesday, 21 January 2015 08:48:40 UTC+1, yvesloui...@gmail.com wrote: I tried with graylog2-web 0.92.4 and this morning with graylog2-web-interface-1.1.0-SNAPSHOT-20150115173058, without success. FWIW, the Graylog web interface usually just works with the matching version of the server. So if you've tried graylog2-web-interface 1.1.0-SNAPSHOT with graylog2-server 0.92.4, that most probably didn't work because they're incompatible. Cheers, Jochen -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+u...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
