Hi John,
please check the logs of your Graylog server and the contents of the
Developer Console in your web browser.
Cheers,
Jochen
On Thursday, 2 June 2016 01:10:47 UTC+2, John Babio wrote:
>
> Back to broken
>
>
> We are experiencing problems connecting to the Graylog server running on
> *ht
Hi Jimmy,
the maximum (GELF) message size can currently not be limited in Graylog.
Cheers,
Jochen
On Wednesday, 1 June 2016 20:33:28 UTC+2, Jimmy Chen wrote:
>
> Is there a way to configure max log message size in Graylog 2.0.1. Our
> input is limited to UDP GELF only.
>
--
You received this
Cool, thanks for the feedback!
Cheers,
Jochen
On Wednesday, 1 June 2016 22:25:06 UTC+2, beeg98 wrote:
>
> I was able to get it going without too many issues. This was my first time
> installing it, so there was a bit of a learning curve, but the software
> itself seems fine.
>
> Thanks,
> BJ
>
Hi Marcin,
you can query the message ID by requesting the field *_id* (notice the
underscore).
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubs
Hello, i'm using graylog 2.0.2.
Today i wanted to use a stream to get email alert. But it seems there is a
problem.
The stream rule works and my logs are redirected to it.
I have configured the condition to trigger alerts like so:
If i send test e-mail it works.
But when i receive a log that
Hi Cazy,
Thanks for your response. Seems that will work for me:)
Thanks for help:)
Marcin
On Thursday, June 2, 2016 at 11:19:45 AM UTC+2, cazy wrote:
>
> Hi Marcin,
>
> you can query the message ID by requesting the field *_id* (notice the
> underscore).
>
>
--
You received this message be
Hi Chad,
I had a similar issue for which I found a solution: I think the reason for
your non-match is that regex() needs the pattern to match fully on the
message string. Try to modify your pattern to something like "^.+SomeProc
*.**".
*@ Jochen:* Could you comment on that? I think the reason i
Hi,
Here are few rules from different streams
*message* must match regular expression *RuntimeException: No Elastic
Search server found for partner *
*full_message* must match exactly *"Cannot find" *
- *message* must match regular expression
*java.util.concurrent.TimeoutE
Well, "out of the box", no that didn't work. I've got faith that it can be
done using this approach, but we'll also need to utilize Elastic's "de_dot"
filter plugin. I'm hoping to make some progress with that today, and I'll
provide an update by the end of the day. I've got about 10 fires to p
Hi,
I need search in case insesitive mode in extracted fields of message.
I try use solutions described in this post :
https://groups.google.com/forum/#!topic/graylog2/xunuSZPgGIc
>
But with no positive effects.
I plan paste some piece with example code but before I will do this - Maybe
som
Unable to locate said user in those areas. For the sake of clarity; this
account was initially used to setup LDAP, but was done so in error. LDAP
was then reconfigured with the correct credentials. It's like Graylog has
somehow held onto this incorrect ldap configuration, somewhere, but I c
Hi Robert,
check the "ldap_settings" collection in MongoDB and make sure that only 1
entry exists in there.
Cheers,
Jochen
On Thursday, 2 June 2016 15:07:37 UTC+2, Robert Hough wrote:
>
> Unable to locate said user in those areas. For the sake of clarity;
> this account was initially used t
Thanks for the reply. Is there way to see how big the messages are then?
On Thursday, June 2, 2016 at 12:46:40 AM UTC-7, Jochen Schalanda wrote:
>
> Hi Jimmy,
>
> the maximum (GELF) message size can currently not be limited in Graylog.
>
> Cheers,
> Jochen
>
> On Wednesday, 1 June 2016 20:33:28 UT
Good luck with the fires and I'll check back to see how it went.
On Thursday, June 2, 2016 at 6:03:34 AM UTC-7, Robert Hough wrote:
>
> Well, "out of the box", no that didn't work. I've got faith that it can
> be done using this approach, but we'll also need to utilize Elastic's
> "de_dot" filt
Currently we have a cluster of Graylog/ES nodes that is strictly taking UDP
GELF log messages as input. We are noticing high amount of large log
messages being injected into the data nodes and would like to track down
which of the messages are unusually large. My search for a solution first
bro
Having the same issue as well. Curling localhost:12900/system/sessions
shows the is_valid:false return, so I know the API is answering locally.
However, curling the example.com:12900/system/sessions leaves me with (35)
Unknown SSL protocol error in connection. I believe this may be related to
m
I´m a beginner with graylog.
I have trouble to config the persist data configuaration.
Everytime I do "docker-compose rm" and then start again with
"docker-compose up" every "input" is gone.
I have tried to config the node-id path in the graylog.conf file with a
absolut path to a file and also r
I am getting the following error in my graylog log file.
2016-06-02T16:16:55.327-04:00 WARN [BlockingBatchedESOutput] Error while
waiting for healthy Elasticsearch cluster. Not flushing.
java.util.concurrent.TimeoutException: Elasticsearch cluster didn't get
healthy within timeout
at
o
Server currently unavailable
We are experiencing problems connecting to the Graylog server running on
*https://x.x.x.x:12900/*. Please verify that the server is healthy and
working correctly.
You will be automatically redirected to the previous page once we can
connect to the server.
Do you
Also bumping, as I have the exact same problem, and have tried many
different fixes, all to no avail.
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+
20 matches
Mail list logo
