[graylog2] Re: How to properly setup in order to receive multiple Graylog message inputs?

Hi tok, I have installed graylog2 in ubuntu 14 at aws. after completing setup i tried to open web browser in port 9000 but not working. and port when i try to run this cmd i am getting "java -jar /usr/share/graylog-server/graylog.jar server" am getting this error 016-05-21 08:46:22,638 INFO

Re: [graylog2] Re: How to properly setup in order to receive multiple Graylog message inputs?

Hi Tokred, Thanks a lot for your help. Already setup those in Windows machine. I'm going to test it. I see. OK let me have a look on the Stream docs first. Once again thanks a lot, Tokred :-) On Sat, May 14, 2016 at 5:34 PM, wrote: > Hi, > > correct, just set the same Graylog

Re: [graylog2] Re: How to properly setup in order to receive multiple Graylog message inputs?

Hi, correct, just set the same Graylog IP/port as NXLog target on all your Windows machines. The Graylog input adds a "source" field to each message so you can see from which machine the event came from. To filter the messages from your input, have a look at the documentation of streams

[graylog2] Re: How to properly setup in order to receive multiple Graylog message inputs?

Maybe a misunderstanding from my side, but are you familiar with client-server communication? A Graylog input acts as network service (=server role) waiting for messages from an arbitrary number of clients. No need to have a 1-to-1 relationship, i.e. you do not need a separate input per

[graylog2] Re: How to properly setup in order to receive multiple Graylog message inputs?

Dear Jochen, Thanks for your reply. The bind address there mean the IP of our Graylog server IP? If I do so it will give the "Error starting this input: address already in use" Is there any other way instead of changing the listening port? Because maybe more client will be added. :-) On

[graylog2] Re: How to properly setup in order to receive multiple Graylog message inputs?

Hi Arief, you have to provide a specific bind address for the input named "FNIT-WIN-WEB01" and not the wildcard address 0.0.0.0. Alternatively, you can simply change the listening port of one of those inputs. Cheers, Jochen On Friday, 13 May 2016 04:17:46 UTC+2, Arief Hydayat wrote: > > >