Dear friends of Graylog2,
it has come to our attention, that a serious vulnerability in one of the
essential components that we rely on for the development and operation of
Graylog2 has been published. Elasticsearch contains a feature named “dynamic
scripting” which allows you to evaluate MVEL
Hello,
i want to test the graylog2 server . ( CPU 8 x 2,6 Ghz , 4048 Gig RAM)
I send with logger 10.000 messages from *tow *systems with rsyslog over
UDP. (In total 20.000 messages)
But graylog2 shows me only ~ 17.000 messages
tcpdump received 19.980 messages on graylog2 server
If i
Any plans on brining back Live Dashboards?
I really liked it and then it was taken out. So will it be added back in
the future? If its not is there an alternative?
--
You received this message because you are subscribed to the Google Groups
graylog2 group.
To unsubscribe from this group and
There is an alternative, please check out the stream dashboards.
You can find them at this address:
https://github.com/Graylog2/graylog2-stream-dashboard
Have fun,
D.
--
TORCH GmbH
Steckelhörn 11
20457 Hamburg
Tel +49 (0)40-60945200
https://www.torch.sh
Commercial Reg.
We have streams setup to alert as soon as there are messages coming in (eg
more then 0 messages in the last 30 minutes).
We also activated the option to get the last 10 messages.
However it seems that if there is less then 10 messages available, no
messages get sent.
It should be that the email
I found those github issues:
https://github.com/Graylog2/graylog2-web-interface/issues/574
https://github.com/Graylog2/graylog2-web-interface/issues/407
They are marked as solved what am I missing ?
On Friday, 9 May 2014 14:17:33 UTC+12, Benoit Chabord wrote:
Hello,
I can create
Dear All,
Please help me in setting multiple graylog servers on a single graylog web
interface.
ie multiple graylog server are connected by a single web interface.
Thanks
Ankit Mittal
--
You received this message because you are subscribed to the Google Groups
graylog2 group.
To
OK, I spoke too soon. Although I got one of my servers working, I'm now
having the exact same issue on another server (not clustered, completely
separate), and I followed all of the same steps I did last time. This is
really annoying behavior. The master server is accepting messages but no