I think it is sufficient for us to stick to the default configuration without external message queue.
Thanks, Wayne On Wednesday, October 19, 2016 at 9:14:11 AM UTC-4, Jochen Schalanda wrote: > > Hi Wayne, > > On Wednesday, 19 October 2016 15:07:07 UTC+2, Wayne wrote: >> >> It is stated in 2.1 document that Kafka and RabbitMQ can be configured as >> transport queue. >> >> What are the use cases/scenarios which we need to do the above >> configuration considering Graylog already has its own way to persist the >> messages? >> > > It can be useful for connecting offsite locations with bad network > connection or if log messages aren't exclusively consumed by Graylog. > > If you can't come up with a use case for using a message broker like > RabbitMQ or Apache Kafka, it's probably not necessary for you… > > Cheers, > Jochen > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/e8bdc639-f8ba-4d1d-a034-78c7bdd150c8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
