Hi Dmitri, But how to upgrade radio without loosing any messages? >
There are several ways to upgrade Graylog2 Radio without losing messages: - If your clients can buffer log messages, just pause the sending logs to Graylog2 Radio, upgrade it, and resume the sending of logs to Graylog2 Radio afterwards. This is quite unlikely, though. - Maybe your clients already support failover to another Graylog2 Server/Radio node in their logging framework. Unfortunately pretty few (if any?) GELF clients currently support this and it would only be feasible when using TCP. - Add a small buffer in between your clients and Graylog2 Radio, e. g. logstash using its GELF input <http://logstash.net/docs/1.4.2/inputs/gelf> and GELF output <http://logstash.net/docs/1.4.2/outputs/gelf> plugins. You will have the exact same problem when upgrading logstash, though. - Run Graylog2 Radio behind a small proxy or use a packet filter like Netfilter/iptables to be able to send packets arriving for Graylog2 Radio to different (locally running) instances. In this case you can install a second Graylog2 Radio instance on your system and make it listen to a different interface/port. When you want to upgrade on of the instances you can simply reconfigure the proxy or packet filter to forward the packets to the other Graylog2 Radio instance. > And do i need to upgrade radio every time i upgrade server to newer > version? > No, usually this is not necessary. If we make breaking changes in the message format used by Graylog2 Server and Graylog2 Radio, we'll announce this in the release notes. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
