And that still doesn't work? If you are on the Inputs page, do you see any
bytes transferred?
> On Jan 18, 2017, at 6:41 PM, Benbrahim Anass wrote:
>
> netstat -pant | grep
> tcp6 0 0 ::: :::*LISTEN
>
netstat -pant | grep
tcp6 0 0 ::: :::*LISTEN
886/java
tcp6 0 0 172.16.52.25: 172.16.52.23:40093
ESTABLISHED
So you have Raw TCP input on that same port? Can you see the port listening,
and can you telnet to it from the logstash host?
> On Jan 18, 2017, at 6:03 PM, Benbrahim Anass wrote:
>
> I tried the minimal config:
> tcp {
> host => "172.16.52.25"
> port => 5445
> }
>
> with the raw tex
I tried the minimal config:
tcp {
host => "172.16.52.25"
port => 5445
}
with the raw text input as you said, i recieve nothing in graylog, but i
see that logstash is forwarding everything
cheers
Anas
Le mercredi 18 janvier 2017 09:35:01 UTC+1, Richard S. Westmoreland a
écrit :
>
> Raw
Raw TCP Input
> On Jan 18, 2017, at 4:28 PM, Benbrahim Anass wrote:
>
> i already parse everything using json, if like you said i use TCP output,
> what input in graylog should i use?
>
> cheers
> Anas
>
> Le mardi 17 janvier 2017 12:01:17 UTC+1, Richard S. Westmoreland a écrit :
>>
>> Ah s
i already parse everything using json, if like you said i use TCP output,
what input in graylog should i use?
cheers
Anas
Le mardi 17 janvier 2017 12:01:17 UTC+1, Richard S. Westmoreland a écrit :
>
> Ah sorry, TCP. If he sets it to JSON then an extractor should parse that
> back out easily.
Ah sorry, TCP. If he sets it to JSON then an extractor should parse that back
out easily.
https://www.elastic.co/guide/en/logstash/current/plugins-outputs-tcp.html
> On Jan 17, 2017, at 7:54 PM, Jochen Schalanda wrote:
>
> Hi Richard,
>
>> On Tuesday, 17 January 2017 11:51:40 UTC+1, Richard
Hi Richard,
On Tuesday, 17 January 2017 11:51:40 UTC+1, Richard S. Westmoreland wrote:
>
> If you're just trying to connect Logstash and Graylog over TLS, I think
> getting AMQP would be overkill. You should start with getting the TLS cert
> ready, then enable a GELF TCP Input with TLS, then co
If you're just trying to connect Logstash and Graylog over TLS, I think getting
AMQP would be overkill. You should start with getting the TLS cert ready, then
enable a GELF TCP Input with TLS, then configure Logstash to send to that.
> On Jan 17, 2017, at 7:12 PM, Benbrahim Anass wrote:
>
>
Thanks man, it seems that rabbitMQ broker needs to be installed somewhere
first and from there graylog extract recieved messages if i got this right
using the broker URL
please correct me if i'm wrong
about kafka, i didnt find a way to use TLS with it
cheers
anas
Le mardi 17 janvier 2017 10:5
Hi,
in case you want to use AMQP (RabbitMQ), I'd recommend reading up on the
terminology and details first:
- https://www.rabbitmq.com/getstarted.html
- https://www.rabbitmq.com/admin-guide.html
- https://www.rabbitmq.com/how.html
There are other ways to send messages from Logstash
for exemple broker hosname, when i put localhost : connexion denied , i
dont know what to put there.
routing key : no idea what is that
cheers
Anas
Le mardi 17 janvier 2017 10:05:03 UTC+1, Jochen Schalanda a écrit :
>
> Hi,
>
> On Tuesday, 17 January 2017 09:35:02 UTC+1, Benbrahim Anass wrote:
>
Hi,
On Tuesday, 17 January 2017 09:35:02 UTC+1, Benbrahim Anass wrote:
>
> i tried gelf AMQP but i had difficulties configuring it
>
What exactly didn't work for you?
Cheers,
Jochen
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubs
13 matches
Mail list logo
