-Server-URL
"https://graylogserver.example.com/api;
RewriteCond %{REQUEST_URI} ^/api
RewriteRule ^/(api\/)(.*) http://127.0.0.1:12900/$2 [P,L]
Order allow,deny
Allow from all
Regards
Micha
--
You received this message because you are subscribed to the G
to just 200 and
test if the pool stays up - if that doesnt work also - i guess there is a
problem somewhere else.
Greets
Micha
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving e
\nHost: dummy\r\n\r\n
*Receive String:*
Alive
Regards
Micha
Am Mittwoch, 13. April 2016 01:38:35 UTC+2 schrieb Marty:
>
> Hi Folks,
>
> Graylog V1.3.4
>
> Just wondering if anyone has integrated the Graylog LB state into the F5
> native http health check.
> I can't get t
5wvjDgZGI/ABI/LC67YWfMjBgL7v83yk_IBDQbzjIHuQboA/s1600/config_changed_map.png>
Thank you so far :)
<https://lh3.googleusercontent.com/-2FjsWE3k_CE/Vv5wm2TkQXI/ABA/lUz4B0F5gNcW2JFef3fpYhjVSk7SvxCbQ/s1600/config_changed.png>
Am Freitag, 1. April 2016 14:40:38 UTC+2 schrieb M
tag, 1. April 2016 14:31:50 UTC+2 schrieb Edmundo Alvarez:
>
> It looks like it's running before extractors in your Graylog instance.
> Could you please share with us your "Message Processors Configuration" in
> System -> Configurations?
>
> Edmundo
>
>
at
> org.graylog2.shared.buffers.processors.ProcessBufferProcessor.onEvent(ProcessBufferProcessor.java:35)
>
> [graylog.jar:?]
> > 2016-04-01_07:21:22.18660 at
> com.lmax.disruptor.WorkProcessor.run(WorkProcessor.java:139)
> [graylog.jar:?]
> > 2016-04-01_07:2
