Home » Microsoft Operations Manager 2005 » Linux, Syslog and System Center Operations Manager 2007


Welcome to contoso.se! My name is Anders Bengtsson and this is my blog about Azure infrastructure and system management. I am a senior engineer in the FastTrack for Azure team, part of Azure Engineering, at Microsoft.  Contoso.se has two main purposes, first as a platform to share information with the community and the second as a notebook for myself.

Everything you read here is my own personal opinion and any code is provided "AS-IS" with no warranties.

Anders Bengtsson

MVP awarded 2007,2008,2009,2010

My Books
Service Manager Unleashed
Service Manager Unleashed
Orchestrator Unleashed
Orchestrator 2012 Unleashed
Inside the Microsoft Operations Management Suite

Linux, Syslog and System Center Operations Manager 2007

We all know that there is no pure Microsoft environment. There is for example often a old Linux box, and that box need to be monitored as well as everything else. If you answer “no, it dont”, why dont you shut down that box immediate? In this post I will show how to get syslog messages from a Linux machine (Red Hat Fedora 6) into your Operations Manager 2007.

First you will have to modify your Linux to forward messages to your Operations Manager machine, and then create a rule in your Operations Manager server.

You will have to modify your Linux to forward messages to your Operations Manager machine. That you will do in the /etc/syslog.conf file. At this screendump you can see that I have added one line that will send all messages (*.*) to my Operations Manager server ( After added that line, and save changes (:wq!), you will have to restart the syslog service, that you can do with “service syslog restart”. There are a lot of settings that you can do in the syslog.conf to only forward some category of messages.

After that the Linux side is finish. As you can see with the “netstat –an” your Operations Manager server is not listening to the standard port (UDP port 514) by default. Your server will not do that until you have an active rule (not disabled) that use SysLogDS as data source. To create a rule to collect your syslog messages,

  1. From the Start Menu, select the SCOM Operations Console
  2. In the Navigation pane (left), Click Authoring
  3. In the Authoring pane, right click Rules and choose “Create a new rule…” from the context menu
  4. On the Select a Rule Type screen, select Alert Generating Rules\Event Based\Syslog (Alert), click Next
  5. On the General screen, input a suitable rule name and a description, click select and choose your management server in the select a target type window (select the machine that will recive syslog messages), click OK, back on the General screen, click Next
  6. On the Build Event Expression screen, create an expression, unfortunately I have not figur how to build a good expression. Input a expression and then delete it later. Click Next
  7. On the Configure Alerts screen, input an alert name, priority and severity. In the Alert description box, input as this screenshot. If you dont do this there will be no alert description in the console. With this config you will get a alert description like below. Click Create.
    Alert in Console
  8. In the Rules pane, right click your new rule and choose “Properties” from the context menu
  9. On the rule properties screen, click the Configuration tab
  10. On the rule properties screen and the configuration tab, click Edit under Data Sources
  11. On the expression screen, select the expression and click Delete. Click OK
  12. On the rule properties screen, click OK

That should do it!

Now we dont have a filter on the Ops Mgr side, but you can filter on the Linux/syslog side, until you have figur out how to do a good filter on the rule. You read about creating filter in this KB from Microsoft. It is about syslog in MOM 2000/2005 but the filter part is the same.




Comments are closed.