No. I have separate machines. Here is my config on one client:
##################################################
server_url: http://10.22.1.107:12900
tls_skip_verify: false
node_id: dev1
collector_id: file:/etc/graylog/collector-sidecar/collector-id
tags:
- auth
- nginx-access
- nginx-error
log_path: /var/log/graylog/collector-sidecar
update_interval: 10
backends:
- name: nxlog
enabled: true
binary_path: /usr/bin/nxlog
configuration_path:
/etc/graylog/collector-sidecar/generated/nxlog.conf
#### EOF ###################################################
I have one collector output with this config:
Name: Gelf-TCP1
Type: [NXLog] GELF TCP Output
Server IP: 10.22.1.107
Port: 12201
Then I have three Collector Inputs:
- auth
- nginx-access
- nginx-error
All configured as:
Forward to: Gelf-TCP1
Type: [NXLog] file input
Path to Logfile: /path/to/the/log
And the rest default
Then I have in System/Inputs one GELF-TCP input with:
Bind address: 0.0.0.0
Port: 12201
And the rest is default
My clients are Debian so I did:
wget
https://nxlog.co/system/files/products/files/1/nxlog-ce_2.9.1504_debian_jessie_amd64.deb
dpkg -i nxlog-ce_2.9.1504_debian_jessie_amd64.deb
/etc/init.d/nxlog stop
update-rc.d -f nxlog remove
gpasswd -a nxlog adm
wget
https://github.com/Graylog2/collector-sidecar/releases/download/0.0.8/collector-sidecar_0.0.8-1_amd64.deb
dpkg -i collector-sidecar_0.0.8-1_amd64.deb
graylog-collector-sidecar -service install
service collector-sidecar start
systemctl status collector-sidecar.service
I hope it will help.
Regards,
Marko
On Friday, June 10, 2016 at 7:53:39 AM UTC+1, Joshua Humpich wrote:
>
> Hey Marko,
> did you run the server and the collector-sidecar on the same machine?
> or does the collector-sidecar runs on another machine without a graylog
> server instance?
> I also try to get this run remotely with two machines... but still without
> access
>
> Regards,
> Josh
>
>
> Am Donnerstag, 9. Juni 2016 17:15:40 UTC+2 schrieb Marko Lerota:
>>
>> I managed to get it working. :-). There are few steps needed to be done
>> before installing and running
>> sidecar and this is not covered in official documentation so it's little
>> confusing. People new to Graylog
>> will find it difficult to understand what's needed to be done first. The
>> steps I needed to do
>> before running sidecar are:
>>
>> 1. Create one Gelf-input in System/Inputs
>> 2. Configure output in Collector Configuration (Type-NXLog GELF TCP
>> Output, IP, Port 12201)
>> 3. Create Collector Inputs
>>
>> And then sidecar can work.
>>
>> Thanks Marius
>>
>> On Thursday, June 9, 2016 at 3:12:07 PM UTC+1, Marius Sturm wrote:
>>>
>>> You can start the Sidecar in foreground as root and watch for error
>>> messages. Just execute it without any options.
>>> Is NXLog complaining about the missing config file or the Sidecar itself?
>>> Did you tag your configuration in the web ui and on the client side with
>>> the same string so that a configuration file is actually rendered?
>>>
>>>>
>>>>
--
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/ce3a9b46-cc50-418b-a0cd-115f6f16a5fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
