netstat -pant | grep 5555
tcp6 0 0 :::5555 :::* LISTEN
886/java
tcp6 0 0 172.16.52.25:5555 172.16.52.23:40093
ESTABLISHED
886/java
output {
tcp {
host => "172.16.52.25"
port => 5555
}
nc -vz -t 172.16.52.25 5555
Connection to 172.16.52.25 5555 port [tcp/*] succeeded!
Le mercredi 18 janvier 2017 10:34:42 UTC+1, Richard S. Westmoreland a
écrit :
>
> 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 <[email protected]
> <javascript:>> wrote:
>
> 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 TCP Input
>>
>> On Jan 18, 2017, at 4:28 PM, Benbrahim Anass <[email protected]> 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 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 <[email protected]>
>>> wrote:
>>>
>>> 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 configure Logstash to
>>>> send to that.
>>>>
>>>
>>> Logstash currently doesn't support GELF TCP.
>>>
>>> Cheers,
>>> Jochen
>>>
>>> --
>>> 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 [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/graylog2/158fdceb-e02c-46f1-9d38-33e3f67ae4d4%40googlegroups.com
>>>
>>> <https://groups.google.com/d/msgid/graylog2/158fdceb-e02c-46f1-9d38-33e3f67ae4d4%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/graylog2/39f3c880-b027-4571-936d-854f4b0b3ea8%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/graylog2/39f3c880-b027-4571-936d-854f4b0b3ea8%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
> 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 [email protected] <javascript:>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/graylog2/193be34b-1038-4d11-85c1-c4f2138e8856%40googlegroups.com
>
> <https://groups.google.com/d/msgid/graylog2/193be34b-1038-4d11-85c1-c4f2138e8856%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/50920268-053b-4ff8-8259-7eaa70b6373c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
