2018-10-22 04:29 AM
Hello
We have a system that writes to the application log.
I can collect other application log messages, but the particular messages written by this application are not rendered correctly.
What I can see is:
%NICWIN-4-Application_1_BLAH: Application,rn=191245 cid= eid=,Sun Oct 21 23:15:17 2018,1,BLAH,,Classic,mycomputer.mydomain.com,0,,
Here you can see that the event is truncated.
Now other application logs are displayed correctly so the collecting user is a member of the event log readers group.
If I look in the XML of the event in the Microsoft Event Viewer then it has the following fields
2018-10-29 04:27 AM
Hi Arnab Chakraverty is this likely to be possible?
2018-10-29 05:26 AM
Hi David,
I do not have an idea on how these said messages are getting generated and how they are being published in the channel.
2018-10-30 08:47 AM
I managed to bodge a work around for this.
1) Set up the event source for winrm collection as normal, and confirm you are getting events in (even if they are truncated)
2) Put the event source into debug verbose mode.
3)This causes all events to be written to the /var/log/netwitness/logcollector/ log files
4) Change the size of the Log Files to 10MB. This causes them to rollover more frequently
5) Grab events out of log files and re inject them into the system
2018-10-30 04:36 PM
Hi David,
Just being curious here, could you not directly send the CEF logs to VLC or LD 514 port from the event source itself? Why do we need a Windows Layer, as it seems to be a custom channel.
with regards
Arnab Chakraverty
2018-10-31 05:10 AM
Hi Arnab Chakraverty that would be the ideal solution. Unfortunately the application only supports writing to the windows application log, and I don't have control over it. Sending via syslog would be so much easier!