Hi Alex,
did you upgrade both, the Graylog server and the web interface, to version
1.1.5?
What kind of queries are you using in your dashboard widgets? Do those
queries complete fast and at all if you enter them in the search bar? You
can also click on the icon on the dashboard widgets to
I'm experiencing the same issue. I'm using the rules located
here:
http://www.virtualizetheworld.com/2014/04/graylog2-extractors-for-fortigate.html
What version are you running on?
root@graylog:/root# tail -f /var/log/graylog/server/current | grep rules
2015-07-29_18:12:11.32634 WARN
I meant to reply here earlier. For some reason drools didn't like the
syntax of the REGEX string I was using. I spun up a test environment so I
could rapidly stop/start graylog and test the rules.
--
You received this message because you are subscribed to the Google Groups
Graylog Users
This is possibly a little obscure but also possibly useful...
I've written a Nagios plugin (in Perl) to check the health of all my
Graylog nodes but the one thing I can't seem to find how to check is the
status of a Graylog node in relation to being able to connect to the
MongoDB. I can check
Jason,
thank you for the report. We have a similar issue open:
https://github.com/Graylog2/graylog2-server/issues/1105
We haven't been able to reproduce this. I will try again with your
setup. Can you send us the syslog-ng configuration snippet for Graylog?
That would be helpful.
Thanks,
Hi Jochen,
Many thanks for the prompt reply. It works exactly as you described it.
Best Regards,
Emde
On Tuesday, July 28, 2015 at 5:48:47 PM UTC+3, Jochen Schalanda wrote:
Hi,
the session handling of Graylog is kind of special (i. e. using a very
custom mechanism).
You'll have to use
It looks like index size issue, because new indexes are created faster
than retention process tries to remove old indexes. So, even with
index size about 1M all looks good.
--
WBR,
Eugene Prokopiev
--
You received this message because you are subscribed to the Google Groups
graylog2 group.
To
I have setup my Juniper to send data in via syslog to my graylog server
1.1.5. I am seeing the data arrive via tcpdump on the destination server,
but it is not ingested into graylog. I am using that same port to ingest
other syslog data with no issues. Where should I look next for
