From the NLS GUI, using a filter definition is likely to trip things up a bit due to how it gets translated into the logstash configuration files. Try removing filter:
The logstash documentation is correct though, it's just a quirk of how things are handled via the NLS GUI. Check out /usr/local/nagioslogserver/logstash/etc/conf.d/ to see what i'm talking about in terms of how the GUI input gets translated into configuration files.
The input filter I am using is 'import_raw' and adding a tag 'auditd'. The filter is based on incoming event with that tag. At least KV should be creating fields where key=value but that is not happening... HELP.
Thanks for the info but I ran into another issue. I did not apply the changes you suggested yet. When I logged in this morning all the inputs and filters, in the GUI, were gone. All blank. However in ../etc/conf.d the input and filter conf files are still present with all the proper configurations. It's seems like NLS is not loading them. I performed a restart on both logstash and Elasticsearch but that did not correct the issue.
Permissions on the files are rwxrwxr-w and owned by nagios nagios. This has always been the case. Not sure what would be causing this.. What is funny, even though the GUI says the inputs are gone, data is still coming in on the port that were defined, just now everything is coming in due to everything not loading.
If there were no inputs, generally logstash will fail after a while. As a frame of reference, could you show us what your global configuration page looks like currently?