Thats fairly useless when you are using graylog in an automated setup.
If I need to set it up with (the old) syslog_listen_port on 8140 then it
was a simple config entry that could be added on build. Its not practical
to build 10 environments with graylog and then have to log into 10 web
interfaces to reconfigure.
is there a rest endpoint that i can use to do this on?
On Sunday, 13 October 2013 19:17:18 UTC+1, Kay Röpke wrote:
>
> Hi!
>
> We should have removed the configuration entries, sorry for that!
>
> You set up the inputs from within the web interface now. Once you are
> logged in, go to the System menu, choose Nodes from the right submenu.
> There on the graylog2 server node, go to the Action menu and choose
> Inputs. From there you can launch as many inputs as you want, on any port
> you want.
> For the privileged ports < 1024 you have to the graylog2-server process as
> root, of course.
>
> Sorry for the confusion,
>
> Kay
>
> On Friday, October 11, 2013 7:45:08 PM UTC+2, Deepak Jagannath wrote:
>>
>> It looks like I have everything setup correctly. However I can't figure
>> out what port, how to configure, or turn on the syslog udp port. I tried
>> 514, 9099, etc. I get connection refused from netcat so I think it's not
>> listening. I'm trying from localhost.
>>
>> echo "Hello Graylog2, let's be friends." | nc -w 1 -u 127.0.0.1 9099
>>
>> Here's my setup:
>> Elastic Search 0.90.5-1 installed via RPM (RHEL)
>> elasticsearch.yml
>> cluster.name: graylog2
>> node.master: true
>> node.data: true
>>
>> Graylog2 Server 0.20.0 preview 2 installed via zip from Github.
>> graylog2.conf
>> is_master = true
>> elasticsearch_index_prefix = graylog2
>> elasticsearch_cluster_name = graylog2
>> elasticsearch_node_name = graylog2-server
>> elasticsearch_node_master = false
>> elasticsearch_node_data = false
>>
>> Graylog2 Web 0.20.0 preview 2 installed via zip from Github
>>
>> Systems status
>> System messages: Started up.
>> ElasticSearch Cluster is green
>>
>> Elasticsearch logs
>> graylog2.log
>> [2013-10-11 17:35:32,034][INFO ][cluster.service ] [Thundra]
>> added
>> {[graylog2-server][PLpmGkraTO6oCJjCHGbIOw][inet[/10.54.10.10:9350]]{client=true,
>>
>> data=false, master=false},}, reason: zen-disco-receive(join from
>> node[[graylog2-server][PLpmGkraTO6oCJjCHGbIOw][inet[/10.54.10.10:9350]]{client=true,
>>
>> data=false, master=false}])
>>
>> Thanks,
>> Deepak
>>
>
--
----------------------------------------------------------------------------------
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this email
by anyone else is unauthorised. If you are not the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be
taken in reliance on it, is prohibited and may be unlawful.
Policy Expert is a trading name of QMetric Group Limited who is authorised
and regulated by the Financial Conduct Authority. The registered company
address of QMetric Group Limited is: 32-38 Dukes Place, London, EC3A 7LP
and its company registration number is 07151701.
--
You received this message because you are subscribed to the Google Groups
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
