Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • I have another question. Would there be any performance penalty associated with process tracking? I fired up Event Viewer on my laptop and saw 16,000 events in the Windows Security Log after seven hours of normal usage.
    – nehalchoy
    Commented Apr 25 at 12:27
  • Like most performance analysis it's subjective and situation-specific. Starting a new console host process isn't free, but it may not be noticeable underneath a certain frequency, especially as the CPU speed and core count increase. In the spirit of avoiding premature optimization, I would probably go with the scheduled task batch approach until it became a problem. Then I'd switch to a permanently resident background process that starts once and subscribes to Event Log, for example in a C# Windows service that uses System.Diagnostics.Eventing.Reader.EventLogWatcher. Commented Apr 25 at 22:49