Hi,
I noticed the NXlog service is not started at the end of the install process. I would the service to start automatically at the end of the install of the MSI.
Our goal is:
- modify the conf file in the MSI file to have it ready out of the box.
- Deploy with GPO on all servers.
Hi,
We are using the community edition of nxlog 2.8.1248 on windows 2008 R2 server. We are having forwarding event log and IIS logs to graylog2.
This is the conf file is pasted below.
Unnecessary syslog header was recorded from 0:00 to 9:00 on Jan 1, 2015 of JST(UTC+9:00).
Example
-----
<133>Dec 31 23:55:04 OTSS0101 OTxx01xx: warning
<133>Jan 1 00:20:12 10.70.0.32 Jan 01 00:21:51 OTSS0101 OTxx01xx: critical
--
<133>Jan 1 08:00:15 10.70.0.32 Jan 01 08:01:52 OTSS0101 OTxx01xx: critical
<133>Jan 1 09:01:51 OTSS0101 OTxx01xx: critical
-----
I am trying to setup a listener on IPv6 (nxlog community edition) and am receiving errors on startup. When using IPv4, it starts without error:
Botond,
Would you consider creating an output module for email? It would be quite useful for generating alerts. While one can use exec_async to send email, it is rather cludgy.
Cheers
Ash
