Hi, Graylog doesn't emulate an AMQP or Kafka broker but it contains a performant and battle-tested message journal which can be used to buffer messages if the backend (i. e. Elasticsearch) is overwhelmed or down.
You could use EasyGelf (https://github.com/Pliner/EasyGelf) to send your log messages to Graylog (with a GELF UDP input). Cheers, Jochen On Friday, 2 October 2015 09:47:15 UTC+2, [email protected] wrote: > > The Graylog v.1.0 GA annoucement states: > "Send your messages directly to Graylog (through a load balancer if > required) and uninstall any buffering technology like AMQP, Kafka or Redis > that might sit in front." > > If we are to stop using our rabbitmq server and make our amqp clients go > directly to Graylog, which graylog input are we supposed to use? Seems like > GELF AMQP and Raw/Plaintext AMQP act as clients for a AMQP server like > rabbitmq? > > To be honest, the information in that announcement is a little confusion... > > Anyone who could point us to some detailed relevant documentation? > > We currently use https://github.com/haf/NLog.RabbitMQ for our > applications, which forward their logs into a rabbitmq cluster, which a > older version of graylog radio is picking up, but we are looking into > migrating to the new graylog 1.2... > -- 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/e5bb9a05-1413-42dd-8d28-53bb528ab7f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
