NXLog for Windows - include_stdout not working

#1 ADE 7 years ago

This is my input module

Module im_file include_stdout %ROOT%\get_iis_log_paths.cmd if $raw_event =~ /^#/ drop(); else { w3c_parser->parse_csv(); $EventTime = parsedate($date + "T" + $time + ".000Z"); }

In the nxlog.log file I see the following error message

2017-12-06 13:27:02 ERROR invalid keyword: include_stdout at C:\Program Files (x86)\nxlog\conf\nxlog.conf:62 2017-12-06 13:27:02 ERROR module 'iis_w3c' has configuration errors, not adding to route 'IIS_Site1' at C:\Program Files (x86)\nxlog\conf\nxlog.conf:107

Any help would be appreciated

Permalink

#2 b0ti Nxlog ✓ 7 years ago

#1 ADE

Hi, as described in the user manual, I am trying to use a PowerShell script to dynamically get the IIS Log path. The problem is that the include_stdout directive is not being recognized as a valid one. This is my input module Module im_file include_stdout %ROOT%\get_iis_log_paths.cmd if $raw_event =~ /^#/ drop(); else { w3c_parser->parse_csv(); $EventTime = parsedate($date + "T" + $time + ".000Z"); } In the nxlog.log file I see the following error message 2017-12-06 13:27:02 ERROR invalid keyword: include_stdout at C:\Program Files (x86)\nxlog\conf\nxlog.conf:62 2017-12-06 13:27:02 ERROR module 'iis_w3c' has configuration errors, not adding to route 'IIS_Site1' at C:\Program Files (x86)\nxlog\conf\nxlog.conf:107 Any help would be appreciated

If you are referring to the NXLog User Guide I think the very first section should give you a reason for this if you are using the NXLog Community Edition:

Though most of the content applies to all versions of NXLog Community Edition and NXLog Enterprise Edition, this guide was written specifically for NXLog Enterprise Edition version 3.99.3035. Some features covered by this document may not be available in earlier versions of NXLog and earlier versions of NXLog may behave differently than documented here.