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

Powershell – Log like you mean it

How do you do logging in powershell? Why should you do logging? What should you log? Where do you put your log? How do you remove your log? How do you search your log? All important questions and how you answer then depends upon what your background is like and the preferences you have. This will be a 2 part blog post and this is part 1.


Why should you log?

Well it is not mandatory, however I have 2 reasons:
Help with debugging a script/module/functionSelf documenting script/module/function
Firstly; Do you know any program that does not contain any bugs? Working with IT for the last 2 decades, I cannot name one. When you create scripts/modules/functions, you will create bugs, that is where they live and try to make your life a living mess.

Secondly: Adding a little extra information to your logging will make them self documenting. Do you like writing documentation? Well I normally am not fond of it and use logging while debugging to get two birds with one stone.


What should you log?

Anyt…

Powershell - List information about your WIFI networks

This is just a quick post about this new function I have created. Basically this is a text-output to powershell object output function that uses netsh to query the WIFI information. This illustrates the importance of changing the authentication level on your WIFI-network. No matter if you use WEP/WPA/WPA2 your password is available in clear text in your profile.



Cheers

Tore