Send it by mail
hth,,
Arie
On Wednesday, September 16, 2015 at 3:15:12 PM UTC+2, Edmundo Alvarez wrote:
>
> We saw a similar problem with an alert callback that was created in 1.0,
> it could be the same problem that you are experiencing. Could you share
> with us your
Hello Jochen,
nice work! Is it planned to support IPFIX/AppFlow in the future?
Cheers,
Rainer
Am Mittwoch, 26. August 2015 10:37:35 UTC+2 schrieb Jochen Schalanda:
>
> Hi Marsel,
>
> we will publish a Netflow plugin for Graylog 1.2.0 in the near future. I'm
> not aware of any Netflow plugin
>
>
>>
Hello there, yes is possible to autologin, you can use this html code, I
tested and works. But you need to set a timer or something for what you
want, certanly that can be done with js.
Will be cool to do it with out hardcode the username and password.
**
**
*AutoLogin*
**
*
Hi Rainer,
support for AppFlow is currently not planned but feel free to post a
feature request at https://github.com/Graylog2/graylog-plugin-netflow/issues
.
Cheers,
Jochen
On Thursday, 17 September 2015 10:15:45 UTC+2, RaCo wrote:
>
> Hello Jochen,
>
> nice work! Is it planned to support
Hi,
Is there any way I can extract info about how many rules have been affected
by my drools rules? some kind of metrics of dropped/changed messages
depending on rule. I know I can use log but it's too verbose, all i need is
numbers.
--
You received this message because you are subscribed to
HI,
My workaround is to clone it, and create the callback again if needed.
Arie.
On Thursday, September 17, 2015 at 1:09:38 PM UTC+2, Ubay wrote:
>
> Hello,
>
> We have the same problem after upgrading to 1.2.0. The callbacks created
> before version 1.1.6 are not displayed. We also get the
Thank you but it didn't work for me. I got the error message:
Could not clone Stream
Cloning Stream failed with status: Internal Server error.
In the server.log file the error "Read operation to server localhost:27017
failed on database graylog2" is present again.
Regards.
El jueves, 17 de
Hi Claus,
not all message fields are being analyzed during index time, which enables
wildcard searches in the first place. By default, only message, full_message,
and source are being analyzed. If you want to analyze other message fields
as well, you'll need to create an Elasticsearch index
Hi @all
I'm starting my es docker with params as follow:
docker run -t -p 9000:9000 -p 12201:12201 -p 514:514/udp -p : -e
GRAYLOG_NODE_ID=static-nodename -e GRAYLOG_TIMEZONE=Europe/Berlin -e
GRAYLOG_SMTP_SERVER="my-smtp.server --no-tls --no-ssl" -v /graylog/data:
/var/opt/graylog/data
This seems to be closely related to your issue:
https://www.elastic.co/blog/hot-warm-architecture?blade=tw
Am Mittwoch, 16. September 2015 17:12:45 UTC+2 schrieb
holgerop...@gmail.com:
>
> *Is it possible to move older indices from FS x on SSD to FS y on HDD?*
>
> We want to try this because
I have that error to, but the clone appeard.
We put "Clone" in front of the name of the clone, you have to do that :-)
On Thursday, September 17, 2015 at 2:02:42 PM UTC+2, Ubay wrote:
>
> Thank you but it didn't work for me. I got the error message:
>
> Could not clone Stream
> Cloning Stream
Hi Edmundo,
Thanks!!
The cause of this issue was the "app.js" file which graylog was no able to
load. I fixed it and now the graylog is working fine.
Though it is working fine, when I start the Graylog server component I get
the following lines on console "Failed to load sigar falling back to
Hi,
I'm having an issue with elasticsearch. Any help would be really
appreciated. The first time i had this issue i did a cleanse which fixed
the issue for couple of days, but that deleted all my data.
Every couple of days i'm getting the follwoing error *Elasticsearch cluster
is red.*
The fix works!
Thank you
El jueves, 17 de septiembre de 2015, 14:06:00 (UTC+1), Edmundo Alvarez
escribió:
>
> After looking at the documents provided by Arie and Ubay, I can confirm
> the issue, and we already identified the cause. We are working to provide a
> proper solution for this issue,
After looking at the documents provided by Arie and Ubay, I can confirm the
issue, and we already identified the cause. We are working to provide a proper
solution for this issue, but if you really can't wait, there is a temporary
solution and more information in here:
I am just getting started using graylog, and am honing my logging.
I have a large dump from an external tool im using in my data pipeline that
I want so send as a Debug-level single log item.
I'm interfacing with graylog with nc, piping a formatted string, of GELF
format, to it (ip address
Are you able to do a cat on your elastic search via the api?
https://www.elastic.co/guide/en/elasticsearch/reference/current/cat.html
Do you just have one ES node? Does the logs for elaaticsearch have any errors?
--
You received this message because you are subscribed to the Google Groups
17 matches
Mail list logo
