Monitoring and reporting for Veeam Backup & Replication, VMware vSphere and Microsoft Hyper-V in a single System Center Operations Manager Console
Post Reply
Posts: 34
Liked: 1 time
Joined: Feb 18, 2010 7:51 am
Full Name: Vincent

Syslog Hardware Monitoing MP5 & SCOM 2007

Post by vrm »

SCOM 2007 doesn't have the pre-filters that were available in MOM 2005.

We need syslog events for hardware monitoring because CIM smash will give us not all the hardware information we need.
Because the pre-filters are not longer avaiable in SCOM and we don't want all the syslog events in SCOM and in the SCOM database we looking for another solution.

Is there another way to workaround the pre-filter issue?
Posts: 21
Liked: never
Joined: Jan 01, 2006 1:01 am
Full Name: Arseny Chernov

Re: Syslog Hardware Monitoing MP5 & SCOM 2007

Post by arseny »


Syslog events would not be sent directly to SCOM. They would be put into nworksEventLog, where they would be accessible for MP rules on the agent to match event properties. For example:

Target = VMware ESX Server
Event Log = nworksEventLog
Event ID = 900
Event Parameter #5 = esx host “id” property
Event Parameter #11 = use RegExp to match syslog message

Also, you can trim the amount of messages being sent from syslogd to nworks VIC by editing /etc/syslog.conf

Please see page 155 of ... ide_pg.pdf for convenience.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest