7

I'm looking for a Windows eventlog analyzing and monitoring software for Windows Server 2000/2003 (there are some new features in Windows Server 2008.) The feature set should include:

  • real-time monitoring (alerts via email or other messages)
  • definition of events/event groups which are watched
  • multiple-server
  • reporting (daily/weekly etc. reports)
  • nice client tools
  • not necessarily free or open-source, but that would be nice (of course)

Any recommendation or tip how to implement this using standard tools?

Thanks!

ThatGraemeGuy
  • 15,314
  • 12
  • 51
  • 78
splattne
  • 28,348
  • 19
  • 97
  • 147
  • Shopping Questions are Off-Topic on any of the [se] sites. See [Q&A is hard, lets go Shopping](http://blog.stackoverflow.com/2010/11/qa-is-hard-lets-go-shopping) and the [FAQ] for more details. – Chris S Aug 26 '12 at 04:08

6 Answers6

5

I would suggest you use OSSEC. It can agregate all the information in a single server and has a nice web interface that allows you to display the alerts.

mjn
  • 933
  • 2
  • 12
  • 26
Antoine Benkemoun
  • 7,314
  • 3
  • 41
  • 60
3

Zenoss Core...

2

I use a set of custom Perl scripts. They do several things but the main one goes through the event logs of each of the servers, extracts the warnings and errors for the last 24 hours, creates an Excel spreadsheet with the results and puts that in a folder I check each morning. This way I get the interesting bits in an easy to read format.

I'm currently considering the practicality of integrating event log monitoring with Nagios. With the right kind of ignore filters (e.g. I really don't care that a print job failed) I should only receive alerts that need to be looked into. That's a fair bit of work to set up but I only need to do it once and it will make my job easier long term. Alternatively, I may have another look at Zenoss.

John Gardeniers
  • 27,262
  • 12
  • 53
  • 108
1

I can recommend NOT using GFI event manager. It's a huge bandwidth hog (streams entire logs over the wire repeatedly) and if you have t1 remote sites, this is a big deal. Also, it's flaky, so it requires far too much upkeep for what should be a simple solution.

SecureWorks has a solution that we will be trying. It looks pretty good.

therulebookman
  • 340
  • 2
  • 4
  • 9
1

Splunk (www.splunk.com)

Noah Campbell
  • 599
  • 2
  • 8
  • 15
0

Event Tracker http://www.prismmicrosys.com/eventTracker.php

occam
  • 11
  • 1
  • 4