After going through some further testing I've filed this at https://github.com/Graylog2/collector-sidecar/issues/37 - it looks to be an issue with NXlog CE handling the input and output modules as GUIDs.
On Thursday, 7 July 2016 17:11:41 UTC+1, Kev Johnson wrote: > > Firstly: I love the idea of being able to push out updated configuration > files to my collectors. That said: I'm having issues getting logs to my > Graylog box (deployed from the OVA) > > Steps taken so far are as follows > > > - Installed NXlogCE > - Uninstalled the NXlog service > - Installed the Graylog Collector Sidecar > - Edited the sidecar_collector.yml file to point to my Graylog server, > and remove the reference to IIS > - Installed the Graylog Collector Sidecar service > - Started the Graylog Collector Sidecar service > - Created a configuration (Windows Logs, ship to the UDP GELF Input > defined on my Graylog box) > - Created a tag called Windows and applied it to this configuration > > > I see the nxlog.conf get created on the Windows server, I see nxlog.exe > start up on server, but nothing is sent. TCPDump on the Graylog server > shows only the TCP connections in on port 12900 from the Windows server. > > Any advice on troubleshooting this would be much appreciated! > > -- 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/e230b2cf-e477-41e2-928a-74b42a76463a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
