Skip to main content

Monitoring Orchestrator runbook events from Operations Manager

Today I will follow up on my colleague’s post Mr ITblog (Knut Huglen) about monitoring Orchestrator Runbook events.  He has build a nice double up SNMP loopback feature that does self monitoring in Orchestrator resulting in entries written to a special Windows Eventlog. Now we need to raise alerts in SCOM when one of his runbooks fails or sends a platform event, who knows there could be trouble lurking in his paradise.

We are not going to do anything fancy, however these are the steps we will be focusing on today:

  1. Create a Management Pack for our customizations
  2. Create rules that collects the events from the orchestrator server
Off we go then and fire up the SCOM console and a powershell window. First we create a MP, I am going to use powershell to do this, however you may use the SCOM console as well (Administration – ManagementPacks – Action: Create Management Pack):

image

Import the Management Pack into SCOM and move on to the Authoring section in the SCOM console. Create a new rule:

image 


Give the rule a name and remember to disable the rule (remove the check in “rule is enabled”):


image

Select ad/or browse your Orcestrator server and find the eventlog created in Knut’s post (see link above):

image

image

If you like you could create a filter using “Event level less than Information” to collect all events on level warning and error, however you may want to create two separate rules to control the alert level on the next screen:

image

Next you can create a new rule and filter on Event Level Warning to create alerts with severity level warning in SCOM.


Since we created the rule as “disabled”, we will have to create an override to enable the rule for the Orchestrator server(s). We will use the group “Orchestrator Runbook Servers Group” that comes with the Management Pack from Microsoft. Right click your rule and select “Overrides – Override the rule – For a group” and search for the group in question.


image

image

Create an test platform event of type Error and test your rule. You should have something like this:

image

That is it. Keep spreading love and understanding!

Cheers

Comments

Popular posts from this blog

Build your local powershell module repository - ProGet

So Windows Powershell Blog released a blog a couple of days ago (link). Not too long after, a discussion emerged about it being to complicated to setup. Even though the required software is open source (nugetgalleryserver), it looks like you need to have Visual Studio Installed to compile it. I looked into doing it without visual stuidio, however I have been unable to come up with a solution. I even tweeted about it since I am not an developer. Maybe someone how is familiar with “msbuild” could do a post on how to do it without VS.

Anyhow one of my twitter-friends (@sstranger) came to the rescue and pointed me in the direction of ProGet, hence the title of this post. ProGet comes in 2 different licensing modes
Free (reduced functionality)Enterprise (paid version with extra features)The good news is that the free version supports hosting a local PowershellGet repository which was my intention anyway. So off we go and create a Configration that can install ProGet for us. This is the conf…

Serialize data with PowerShell

Currently I am working on a big new module. In this module, I need to persist data to disk and reprocess them at some point even if the module/PowerShell session was closed. I needed to serialize objects and save them to disk. It needed to be very efficient to be able to support a high volume of objects. Hence I decided to turn this serializer into a module called HashData.



Other Serializing methods

In PowerShell we have several possibilities to serialize objects. There are two cmdlets you can use which are built in:
Export-CliXmlConvertTo-JSON
Both are excellent options if you do not care about the size of the file. In my case I needed something lean and mean in terms of the size on disk for the serialized object. Lets do some tests to compare the different types:


(Hashdata.Object.ps1)

You might be curious why I do not use the Export-CliXML cmdlet and just use the [System.Management.Automation.PSSerializer]::Serialize static method. The static method will generate the same xml, however we …