Database Reference
In-Depth Information
Getting ready
It is recommended that you read the
Understanding the OperationsManagerDW schema
re-
cipe in this chapter before following this recipe. You will need to prepare your environment
to author reports following the instructions in the
Preparing your environment to author re-
ports
recipe.
Report Builder
In the following recipes, we will use Report Builder 3.0 to create custom reports for Opera-
tions Manager. You need to be familiar with using Report Builder to manage and author re-
ports. Using Report Builder is explained in
Chapter 3
,
Unpacking System Center Report
Building Tools
.
Before we start authoring our report, we will take a look at the views that are available in
the alert dataset in the
OperationsManagerDW
database.
Alert dataset
The alert dataset can be used to retrieve information about the alerts generated by rules and
monitors in Operations Manager. The alert dataset includes four views that represent the
data. All views are stored in the
Alert
database schema.
Alert.vAlert
The
Alert.vAlert
view contains all the alerts available in the
OperationsMan-
agerDW
database. You can find general information about the alerts, such as
Name
,
De-
scription
,
Severity
,
Priority
,
Category
,
RaisedDateTime
,
RepeatCount
, triggering workflow, and the managed entity it is associated with.
The
Alert.vAlert
view can be joined to the other views in the alert dataset on the
AlertGuid
column.
To retrieve the rule or monitor that triggered the alert, you can join
Alert.vAlert
to
vRule
and
vMonitor
on the
Alert.vAlert.WorkflowRowId
column. The fol-
lowing rule applies:
• If
Alert.vAlert.MonitorAlertInd
equals
1
, then join
vMonitor
to
vAlert.vAlert.WorkflowRowId = vMonitor.MonitorRowId
