Event Logs

 Top  Previous  Next

Currently the following event log records can be logged by this feature:

 

Event ID

Event Description

Example

10400

A process seems to be leaking memory.

The process leakyapp.exe (PID 1234) seems to be leaking Private Bytes memory. If you keep seeing this message in the event log then it is recommended that you monitor the memory consumption of this process closely with performance monitor if you have not already done so.

 

The process is currently using 23453221 bytes of Private Bytes memory, system memory load is 85%.

 

If you are certain that this process is not leaking memory then you can exclude this process from being monitored (Groups -> GROUPNAME -> System Health -> Process Memory) or change the monitoring parameters (contact support@netikus.net for more information) in the registry. If this process is leaking memory then contact the manufacturer of the application for support.

10401

The process processname is not active.

The process eventsentry_gui.exe is not active.

10402

The process processname is active.

The process eventsentry_gui.exe is active.

 

Additional Information for Process Memory Monitoring only:

This message may either be logged as a Warning or an Error:

 

Warning: It is likely that this process is leaking memory, watch for more entries in the event log of this type. You can ignore single occurances of this event most of the time.
Error: It is very likely that this process is leaking memory. If you keep seeing this message (for the same process) in the event log then you should definitely investigate more.

 

If the Log Only Processes that are very likely to leak Memory option is checked then only Error messages will be logged by this feature.

 

All event logs are logged with the Process Memory Monitoring category.