0
responses

Difficulty Parsing IIS Logs and Sending to Loggly

I'm using NXLog to sending Windows events and IIS logs to Loggly. We've recently onboarded a new MSSP and they have asked us to check off all IIS logging fields. This seems to break parsing of IIS logs that need to be sent to Loggly. I've contact Loggly support and they can't seem to come to a resolution.

Below is the code that we had been using for Loggly previously.

AskedFebruary 18, 2021 - 4:20pm
2
responses

nxlog error when tried to use xm_w3c module

Hi,

I'm using a CE where xm_w3c module is not available. So i'm getting below error:

2019-04-09 14:59:30 ERROR Failed to load module from C:\Program Files (x86)\nxlog\modules\extension\xm_w3c.dll, The specified module could not be found. ; The specified module could not be found.
2019-04-09 14:59:30 ERROR Invalid InputType 'w3c_parser' at C:\Program Files (x86)\nxlog\conf\nxlog.conf:94

AskedApril 9, 2019 - 9:13pm
1
response

Invalid Keyword w3c->parse_csv

When attempting to input IIS logs I see the following error: 'ERROR invalid keyword: w3c->parse_csv()'. Has anyone come across this before and knows how I can parse IIS log into a JSON format to input to redis
my config

<Extension _exec>
Module xm_exec
</Extension>

<Extension _json>
Module xm_json
</Extension>

AskedJuly 30, 2018 - 5:06pm
3
responses

IIS7 W3C log parsing fails

Hello Guys,

I have a question about NXLog IIS7 W3C logs. I set NXLog up and it works basicaly but the NXLog logs are full with error messages like this:

AskedApril 26, 2016 - 12:20pm