@timestamp should automatically be filed with the time that the event came into NLS which may not match up with when the actual event occurred. Not ideal, but is this effectively what you're trying to do with a filter? Are the logs not importing at all?
How are the logs being sent over? Ideally you'd want to make this change on the client side - either making sure the logs include the timestamp or the client sending the data timestamps it.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
The issue is when using the %{TIMESTAMP_ISO8601:logdate} filter to pull out the date (so that the events display properly over time), the parsing fails and all subsequent filters fail as well.
Your assistance in achieving this would be appreciated.
Can you attach a copy of the input, filter, and a sample of the log(sanitized if needed)? Also, are the logs coming over via syslog or nxlog? It'd be good to gather either the rsyslog.conf or nxlog.conf file as well.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
I was trying to do this in rsyslog, it would be the simplest solution so far but rsyslog seems to be cryptic and buggy. In the end I resorted to an ugly hack of running a screen session with tail output with awk to create a new file, but this is not a long term solution as it dies every day at 0000 when the logs rotate. Enough for a proof of concept but nowhere near production-grade.
I've been through the rsyslog5 and rsyslog7 config and man pages for this on Centos6, didn't really get anywhere because it seems it is cryptic and ill behaved, which is unfortunate.
I would prefer to do this with an input filter in NagiosLog, can you please advise exactly what is needed for this?