Saminnet-Search Article Wiki Forum Piwigo SNS Cloud vtiger Sugar

  • Data-Articles
    • Baja iwf (106) Sun09,20:21pm

      sesuai post saya yang terakhirツdisini, rumah dua pohon sedang dalam pembangunan tahap 2 dengan material utama menggunakan baja. baja adalah material konstruksi yang paling padat apabila dibandingkan dengan beton dan kayu karena memiliki berat satuan yang cukup besar. karena baja bisa difabrikasi di pabrik, pemasangan di site bisa lebih cepat dibandingkan dengan beton yang mesti dicetak dan ditun…



A couple of weeks ago I used the SCSM SCOM Alert Connector. When using the connector Alerts from SC Operations Manager are synced to SC Service Managerツand incidents are created based on an Incident Template. You can create rules in SCSM to specify for which alerts specific Incident templatesツare used. But that窶冱 all you can do at the SCSM side. Forツallツalerts which come through the connector an incident is created. We allツknow thatツSCOM can be a bit noisy, so how can we filter the SCOM Alert Connector?

When the Alert connector is added to SCSM and when it窶冱 initialized for the first time a subscription in the product connector in SCOM is created. Based on this subscription alerts will or will not be sendツto SCSM. The subscription is your starting point for filtering alerts in the SCOM Alert Connector:

You can filter on the following:

  • Approved Groupsツ(You can specify from which groups alerts are send to SCSM)
  • Approved Targetsツ(You can specify from which targets alerts are send to SCSM)
  • Criteriaツ(You can specify alert criteria for the alerts which are send to SCSM)

SCOM_Connector_Criteria 300w, 800w" sizes="(max-width: 500px) 100vw, 500px" style="margin: 0px auto 20px; height: auto; max-width: 100%; clear: both; display: block;">

With above options you can configure some filtering. But most of the times it does not completely fit the requirements. So if you want to do some more in-dept filtering on alerts which will be send to SCSM you have to look into other solutions. In this blogpost I want to present a solution which I created. This solution uses System Center Orchestrator for filtering. The solution consists of the following steps:

  1. SC Orchestrator Runbook which monitors new alerts;
  2. SC Orchestrator Runbook which evaluates the filtering rules;
  3. SC Orchestrator Runbook which updates the Alert with a special configured Resolution State
  4. SC Operations Manager Connector Criteria filter based on configured Resolution State

Let we first look into the requirements for this solution. We need to have the correct version of the SC Operations Manager Integration Pack installed on the Orchestrator environment. More information can be foundツhere. If we have installed the OpsMgr IP we can start the Runbook Designer on the Orchestrator Server. In this example I窶冦 going to create a filter based on alerts from specific Management Packs.

  1. The first step is to use theツ窶弄onitor Alert窶ツActivity. Configure this activity to monitor onツNewツAlerts.
  2. Theツnext step is to addツaツ窶賂et Alert窶 activityツto theツrun book. In my case this activity was needed to get some 窶脇xtra窶 information from anツalert.ツThe Management Pack Name parameter is not filled from the Monitor Alert activity. So to get that information I had to use this extra step.
  3. The next step is to add theツ窶漏ead Lines窶ツ activity. This activity reads an external file which holds the list of 窶和llowed窶卍management packs.
  4. The fourth step is to add aツ窶呂ompare Values窶ツactivity. This activity will compare the Management Pack name from the Get-Alert activity and the list of Management Packs from the Read-Lines activity. If there is a match it will continue to the 5th step.
  5. The last step in the runbook is anツ窶篭pdate Alert窶 activity. This activity will update the alert with a 窶special窶 resolution state. First thisツResolution state need to be created in SCOM.

SCOM_Con_Runbook 300w" sizes="(max-width: 714px) 100vw, 714px" style="margin: 0px auto 20px; height: auto; max-width: 100%; clear: both; display: block;">The above imageツshows the runbook we have created. The last step isツto configure the SCOscom_con_toscsmM Alert Connectorツtoツonly send alerts which have the special configuredツResolution State. Based on this Resolution state alerts will be send through the connector to SC Service Manager.

In the above example we have made a filter based onツthe Management Pack Name of an Alert but we can also create filters based on specific times of an alert, names on an alert or we can do correlation of SCOM Alerts based on criteria. So with using SC Orchestrator we have a lot of capabilities in configuring additional filters on the SCSM SCOM Alert Connector.

Thanks toツOskar Landmanツfor working with me on finding a solution for the filtering capabilities!

Category Database

TweetTweet Share on LinkedInShare on LinkedIn Share on Google+Google+ Submit to RedditReddit Publish on WordPress WordPress Send emailSend email