Comments
-
Not in this case. I should add that since my original post here, I have tried the Advanced connector, and it fails with "Corrupt file". I suspect this is due to the connector not handling IIS 10 (server 2019) logs? The only connector I can get to read the logs with the u_ex prefix and _x suffix is the Enhanced 8.5…
-
The X-Forwarded-For data is being captured by IIS, I see it in the logfile. The issue is I cannot get SEM to ingest it. I have a case open for this - I will lets you know how that works out.
-
Found this searching - I am using the "Microsoft IIS Web Server 8.5 (W3C Extended file format) Enhanced Logging" connector, even though my web server is IIS 10 (Server 2019), as there is no Enhanced logging connector for IIS 10. I am not seeing the X-Forwarded-For, or any option to grab it. Do you know specifically where…
-
I know this is an old (and possibly dead) thread, but your comment that you may have a solution intrigues me, as I seek to do both of these - File Audit activity as well as NetApp Syslogs. I could probably mash something together, but if there is an existing solution, so much the better.
-
I am, and I will. I was lurking around here to put off calling support Thanks!