Just for fun, this should be an equivalent setup using HAProxy:  (If you
are a HAProxy guru, please correct this)

backend graylog2
    mode http
    balance roundrobin
    option httpchk GET /system/lbstatus/
    http-check expect status 200
    server web1 10.0.0.10:12900 check
    server web2 10.0.0.20:12900 check
    server web3 10.0.0.30:12900 check

Here is a second HAProxy example that matches the strings provided by
Graylog2.  It accomplishes the same thing, but perhaps is more intelligent
in that it requires Graylog2 to output the string "ALIVE".

backend graylog2
    mode http
    balance roundrobin
    option httpchk GET /system/lbstatus/
    http-check expect string ALIVE
    server web1 10.0.0.10:12900 check
    server web2 10.0.0.20:12900 check
    server web3 10.0.0.30:12900 check




On Wed, Jan 21, 2015 at 9:42 AM, Tristan Rhodes <[email protected]>
wrote:

> I didn't see him specify that he was using GELF format for his logs.  I
> think this is a load-balancer configuration problem.  Here are the values
> you can check with a load-balancer:
>
> "The status knows two different states, ALIVE and DEAD, which is also the
> text/plain response of the resource. Additionally, the same information is
> reflected in the HTTP status codes: If the state is ALIVE the return code
> will be 200 OK, for DEAD it will be 503 Service unavailable. This is done
> to make it easier to configure a wide range of load balancers to be able to
> react to the status."
>
> I have never used keepalived, but I think checking the status code like
> this will work:
>
> real_server 10.x.x.210 xxx {
>      weight 10
>         HTTP_GET {
>                 url {
>                         path /system/lbstatus/
>                         status_code 200
>                     }
>                     connect_timeout 3
>                     connect_port 12900
>                     nb_get_retry 2
>                     delay_before_retry 1
>         }
>     }
>
> Good luck!  Let us know if this works.  (And have you considered using
> HAProxy instead?)
>
> Tristan
>
> On Wed, Jan 21, 2015 at 7:56 AM, Jochen Schalanda <[email protected]> wrote:
>
>> Hi,
>>
>> On Wednesday, 21 January 2015 15:23:01 UTC+1, kutscher wrote:
>>>
>>> Hello, i want to use Loadbalance UDP Syslog Messages to the  Graylog2
>>> Nodes.
>>>
>>
>> Unfortunately that won't be possible because of the chunking mechanism
>> being used when submitting GELF messages via UDP because all chunks must be
>> processed by the same server, see
>> https://www.graylog2.org/resources/gelf/specification.
>>
>> 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.
>>
>
>
>
> --
> Tristan Rhodes
>



-- 
Tristan Rhodes

-- 
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.

Reply via email to