On Monday, September 5, 2016 at 6:59:44 AM UTC-5, Aykisn wrote:
>
> I did this on my three graylog servers:
>
>> sudo rpm -Uvh
>> https://packages.graylog2.org/repo/packages/graylog-2.1-repository_latest.rpm
>> sudo yum update
>>
>
> Then had to restart graylog on my three graylog servers.
>
Hi there
I've been playing around with alerts. The native "email" alert works as
expected, but the HTTP and "Execute command" alarm options lack all detail
about the event that triggered the alert
I've written a script that simply dumps the command line options and
environment vars to a file -
I am also facing same issue, not sure if there is any solution to deal with
it.
Any thoughts?
Regards,
Jay
On Tuesday, April 12, 2016 at 11:13:31 PM UTC+5:30, David Rux wrote:
>
> Hey all,
>
> I have a stream that's set to send an email whenever an alert is triggered
> that matches a channel.
Hi All,
Just now I have learned that I can parse individual keys from json input as
mentioned in below link:
https://github.com/Graylog2/graylog-plugin-pipeline-processor/blob/master/src/test/resources/org/graylog/plugins/pipelineprocessor/functions/jsonpath.txt
But I am wondering, how do I
Hello guys.
I have configurated grayog with alls switches Extreme Networks and work
fine.
But now, I am working with Cisco Router but have the problem in source
message, not put the IP or hsotname Cisco, it start with month, for example
now is Sep.
I show an example: