Very strange. I have tested with a Win7, a Win8.1 and a Win2012R2 node. All with the same negative result.
How did you tested?

My test was like this:

Logwatch section of the agent config:

[logwatch]
ProcessOfflineEvents = yes
Parser = ${ProgramFiles}\NetXMS\var\eventlog-system-parser.xml
Parser = ${ProgramFiles}\NetXMS\var\eventlog-application-parser.xml

Parser (file: eventlog-system-parser.xml):

<parser name="SystemLog">
  <file>*System</file>
  <rules>
    <rule>
      <match>(.*)</match>
      <level>1</level>
      <event params="1">100845</event>
    </rule>
  </rules>
</parser>

Than I hard-switched of the node. After that I checked the NetXMS events of this node. But I can't find any event for the expected Windows Event (Eventlog: System, Event-ID: 6008, Source: Eventlog, Text: Last shutdown was unexpected).
While normal operation I get a NetXMS event for every error in Windows Eventlog. I only have problems with offline events.

thanks
Dani

Best regards,
Victor

is it possible to add the user name of the Windows event log entry to the event parameters?
I monitor a terminal server farm for application crashes which works really nice, but I like to know in the event which user session is affected.

Greetings
Ben

Have you found anything about this?

thanks
Dani

Here the agent log with debuglevel=2. There was no "LogWatch: EvtQuery failed (...)".
There were these events for example before the NetXMS agent started:
Event-ID 41, Source=Kernel-Power, severity=critical, 04.05.2015 18:19:34
Event-ID 6008, Source=EventLog, severity=error, 04.05.2015 18:19:36

thanks
Dani

nxagentd-debug2.log

LogWatch: reading old events between ... and ...

and possibly also like this:

LogWatch: EvtQuery failed (...)

and post those lines and timestamp of "unexpected shutdown" event.

Best regards,
Victor

I tested like this:

parser xml:

<parser name="SystemLog">
  <file>*System</file>
  <rules>
    <rule>
      <match>(.*)</match>
      <level>1</level>
      <event params="1">100845</event>
    </rule>
  </rules>
</parser>

I turned off hardly a Win7-x64 virtual machine and started again. But I don't get an event '100845' in NetXMS for the windows error 6008 (last shutdown was unexpected) in the system eventlog.

Other windows events while the node is normal working are parsed ok and generate NetXMS events.

Best regards,
Victor

it looks perfectly fine. I re-run tests on my system, and agent picks up everything as expected. Let's try to upgrade this system to 2.0-M4 (just to make sure I'm checking latest codebase) , and if it will not help I'll create special build with additional debug.

Best regards,
Victor

thanks
Dani

MasterServers = netxms.domain.com
ListenPort = 4700
RequireAuthentication = yes
RequireEncryption = yes
EnabledCiphers = 1
SharedSecret = longkey
EnableWatchdog = yes
LogFile = {syslog}
LogFile = ${ProgramFiles}\NetXMS\nxagentd.log
DebugLevel = 0
ConfigIncludeDir = ${ProgramFiles}\NetXMS\etc\nxagentd.conf.d
FileStore = ${ProgramFiles}\NetXMS\var
SubAgent = ecs.nsm
SubAgent = portcheck.nsm
SubAgent = ping.nsm
SubAgent = winperf.nsm
SubAgent = wmi.nsm
SubAgent = logwatch.nsm
SubAgent = filemgr.nsm

[filemgr]
RootFolder = ${SystemDrive}\

[logwatch]
ProcessOfflineEvents = yes
Parser = ${ProgramFiles}\NetXMS\var\eventlog-system-parser.xml
Parser = ${ProgramFiles}\NetXMS\var\eventlog-application-parser.xml

Registry Key HKEY_USERS\.DEFAULT\Software\NetXMS\LogParserLibrary:

LogWatch.Application REG_DWORD 0x552b7a44
LogWatch.System REG_DWORD 0x552b7a78

can you please show me your agent config and content of registry entries under HKEY_USERS\.DEFAULT\Software\NetXMS\LogParserLibrary (assuming you run agent under Local System account - otherwise check same registry path under appropriate user)?

Best regards,
Victor

I come back to #2 and #4:

#2: I tested again with V2.0.-M3 but it is not working for me. Can you please check again?

#4: For which version is this planned?

Thanks, Dani

#2 is implemented in 1.2.17. This is turned off by default to maintain compatibility with previous versions. Setting parameter ProcessOfflineEvents in LogWatch section to yes or true will enable this feature. When on, agent will save timestamp of last processed event and on start will process all events since last processed.

Best regards,
Victor

Best regards,
Victor

any plans for #4? To deliver the parser files by agent policy is in my opinion the most elegant way.

Thanks for your information and your work. I agree with all points.

thanks
Dani

I won't be able to help you much. #1, #2, and #4 need changes in agent (#4 also in server). #1 is implemented in 1.2.14 (event source, id, and severity passed as three additional parameters for event generated). #2 should be relatively easy to implement, I'll add this as feature request for 1.2.15. For #4 we plan to introduce new policy type to distribute parser configurations across nodes in a same way as you can distribute configuration files, but I cannot promise exact release when it will be implemented.

Best regards,
Victor