SCOM MP Authoring Example: Generate alerts based on entries from SQL Database (Part 2 of 2)

This is the 2nd part of the 2-part series.  Part 1 can be found here.

In Part 2, I’ll cover the steps involved to create each module type and the rule in this article. all these objects will be created in SCOM 2007 R2 Authoring Console. You can create a new management pack for this or use an existing one.

Firstly, we will need create the probe action and data source modules:

Probe Action Module:

1. Under Type Library pane, go to “Probe Actions” under Module Types and click New—>”Composite Probe Action…”

2. Give it a unique identifier such as “Your.Management.pack.Prefix.Database.Catcher.Probe.Action”

3. in general tab, give it a name:


4. Under Member Modules, add “Microsoft.Windows.PowerShellPropertyBagTriggerOnlyProbe” and give it a Module ID of “PSScript”


5. Click on Edit

6. Enter the ScriptName and TImeoutSeconds. Then Edit again in the Configuration tab of the probe action module


6. When the text editor is launched, Enter the powershell script in between <ScriptBody> and </ScriptBody> tags

7. Below is the script I used in my management pack. please edit it to suit your needs:

#Alarms capture via AuditDB
#Name:        AuditDBAlarmCatcher.PS1
#Param 0:    SQL Database Instance Name
#Param 2:    Database name
#Param 2:    The inteval in seconds
#Author:    Tao Yang
#Date:        07/12/2011


Function Get-LocalTime($UTCTime)
$strCurrentTimeZone = (Get-WmiObject win32_timezone).StandardName
$TZ = [System.TimeZoneInfo]::FindSystemTimeZoneById($strCurrentTimeZone)
$LocalTime = [System.TimeZoneInfo]::ConvertTimeFromUtc($UTCTime, $TZ)
Return $LocalTime

$oAPI = New-Object -ComObject "MOM.ScriptAPI"
$oBag = $oAPI.CreatePropertyBag()
$strServer = ".\$SQLInstance"

$ADOCon = New-Object -ComObject "ADODB.Connection"
$oResults = New-Object -ComObject "ADODB.Recordset"
$adOpenStatic = 3
$adLockOptimistic = 3
$ADOCon.Provider = "sqloledb"
$ADOCon.ConnectionTimeout = 60
$nowInUTC = (Get-Date).ToUniversalTime()
$StartTime = $nowInUTC.AddSeconds(-$Interval)
$conString = "Server=$strServer;Database=$Database;Integrated Security=SSPI"
$strQuery = "Select * from V_Audit Where EventTypeCaption LIKE 'Alarm triggered' AND EventDate >= '$StartTime'"
$oResults.Open($strQuery, $ADOCon, $adOpenStatic, $adLockOptimistic)
$oBag.AddValue('Interval', $Interval)
If (!$oResults.EOF)
If (!([appdomain]::currentdomain.getassemblies() | Where-Object {$_.FullName -ieq "system.core"}))
Try {
Write-Host "Loading .NET DLL into Powershell..." -ForegroundColor Green
} Catch {
#We cannot use Write-Error cmdlet here because $ErrorActionPreference is set to "SilentlyContinue" so it won't display on the screen.
Write-Host "Unable to load .NET Framework into Powershell, please make sure it is installed!" -foregroundColor Red
$oBag.AddValue('GenerateAlert', 'True')
$arrLogEntries = @()
Do {
$EventDate = $oResults.Fields.Item("EventDate").Value
$EventDate = Get-LocalTime $EventDate
$Description = $oResults.Fields.Item("Description").Value
$arrLogEntries += "- $EventDate`: $Description"
} until ($oResults.EOF)
$LogDetail = [System.String]::Join("&#13;", $arrLogEntries)
$intEntryCount = $arrLogEntries.count
Remove-Variable arrLogEntries
} else {
$oBag.AddValue('GenerateAlert', 'False')
$intEntryCount = 0

$oBag.AddValue('LogEntry', $LogDetail)
$oBag.AddValue('LogEntryCount', $intEntryCount)

8. Enter below sections after </ScriptBody> and before <TimeoutSeoncds>:



9. Click Save in the text editor and close it. you should now see what you’ve entered in the configuration tab of the probe action module:


10. Click OK to exit the configuration tab. Under Configuration Schema tab, add 3 parameters (in same order) as shown below:


11. Under Data Types, make sure the input and output data is set as below (should be default anyway):


12. Under Options, I left Accessibility to “Internal”, but if you are going to use this module outside of this management pack, set it to public.


13. Now click OK to exit the probe module window. the probe action module is now created. Now it’s a good time to save the management pack.

Data Sources Module:

1. Under Type Library pane, go to “Data Sources” under Module Types and click New—>”Composite Data Source…”

2. Give it a unique identifier such as “Your.Management.pack.Prefix.Database.Catcher.DataSource”

3. Open the data source module you’ve just created and give it a display name under “General” tab:


4. Add 2 member modules:

Module ID



Next Module

Schedule Data Source System.SimpleScheduler Probe
Probe Probe Action Probe Action module you’ve just created Module Output


5. Edit the SimpleScheduler module, for the IntervalSeconds value, click on “promote…”. this will set it to “$Config/IntervalSeconds$”. and leave SyncTime to blank:


6. Edit the probe action module, use promote to set values for all 3 parameters:


7. Configure “Configuration Schema” tab as below (again, make sure these parameters are in the right order”):


8. Configure Overridable Parameters as below:


9. Make sure output data type is set to System.PropertyBagData


10. Set accessibility to “public” if you are going to access this module from other management packs.

Now the data source module is complete. We are going to create the rule next.


1. Under Health Model pane, go to “Rules” and click New—>”Custom Rule…”

2. Give it a unique identifier such as “Your.Management.pack.Prefix.Database.Catcher.Rule”

3. Give the rule a display name  and select the target class where you want to run the rule under general tab


4. In Modules tab, create a data source module with the type of the data source module type you’ve created previously. give it a module ID of DataSource


5. Edit the data source module configuration, enter the values for all 3 parameters: SQLInstance, Database and IntervalSeconds:


According to above example, this rule will connect to the database “AuditDB” in the particular SQL instance that you specified and will run in every 5 minutes (300 seconds)

6. Now, create a condition detect module with type: System.ExpressionFilter and Module ID: Filter_AlertCondition


7. Edit the condition detection module, under configuration tab, click on Configure… button.

8. Enter the expression as below:

Parameter Name: Property[@Name=’GenerateAlert’]

Operator: Equals

Value: True

Click OK to save.

It looks like this when it’s done:


9. Create an Action module. Type: System.Health.GenerateAlert. ModuleID: Alert.


10. Click Edit for the Action module then click Edit again under Configuration tab to edit the XML.

11. Add below section in the XML before </Configuration> tag:



12. save the XML and exit the text editor. then click on Configure to configure the alert. you may use the parameters from previous step to form the alert description.

13.Edit the Production knowledge of this rule if you like. it will also appear with the alert.

Now we are done. You can save this unsealed management pack or seal it using authoring console. please make sure you test it before import it into your production environment.

Below is a sample alert from my test environment:


Few notes:

  1. The database that I had to work with was a SQL Express DB. I found this free tool extremely useful since I can’t use SQL management studio to connect to SQL Express databases:  Database Browser. The database table screen capture from Part 1 of this series was from this tool.
  2. When testing the PowerShell Script, I needed to run the script under Local Systems as my account did not have access to the database. Since in my script, I connected to the database using integrated security, I had to make sure I run the script under the account which is going to be used to run the rule (in my case, Local Systems), I had to use PSExec from Sysinternals to launch Powershell as it allows me to run executables under Local System.
  3. Originally I used a multi-line string variable in PowerShell script to store records returned from SQL query (one record per line). It didn’t work after added the script to the management pack. I figured out i can use the special HTML character for carriage return inside the string variable in Powershell. So the line looks like this:


My sample PowerShell script can be downloaded from HERE.


  1. Nice.. thanks for sharing.. I am looking at doing something like this myself.. I have to take it to the next step and have the alerts generate from the machine that had the problem..Would be so much easier if my devs would just write to the local Event Viewer.. but oh well. 😉

  2. Hi Tao,

    excellent Post… i dont have words to explain the skill u have acquired in SCOM… My doubt is that in Xpath query the property bag Generate alert type must be boolean right since it is accepting boolean value True/fALSE ? Correct me if i am wrong

  3. Hi Karthick

    It is accepting a string which is either “True” or “False” from the PowerShell code.

    What can sometimes be useful in these sorts of monitoring is to include a reference to the Microsoft.SQLServer.Library and then include a RunAs=”Alias!Microsoft.SQLServer.SQLProbeAccount” as part of the data source module type.

    Great blog Tao Yang.


Leave a Reply

%d bloggers like this: