One method you can use to determine the parameter that
can be defined in a rule is to cause the condition that you want to
trigger the rule on a managed server. After IBM® Sterling Control Center
Monitor captures the data generated by the condition, and written
an event to its events database table, use the IBM Sterling Control Center
Monitor Database Events report to capture the exact contents of
the events in order to examine them.
Procedure
- First, define a new report. In the create report wizard,
after selecting a Report Type of DB Events Report,
click Next.
- For the DB Events Report Filter parameters, specify as
much information as you can to limit the amount of data returned.
- At a minimum, specify a starting and an ending Date/Time
for the report as illustrated in the following table:
| Key |
Operator |
Value |
| Date Time |
Greater than |
Today 0:00 America/Chicago |
The following criteria causes all events
generated between 15:00 and 15:15 to be retrieved. You can specify
additional filter keys as you see fit to limit the size of the report.
| Key |
Operator |
Value |
| Date Time |
Less than |
Today 15:15:00 America/Chicago |
| Date Time |
Greater than |
Today 15:00:00 America/Chicago |
- Click Next when you finish specifying
filter criteria. The Available Columns wizard is displayed.
- Select Date Time, Event Type, and XML_STRING columns
and click Next. The Sort wizard
is displayed.
- Select Date Time and click Next,
and then run the report.
The report generated contains
the events generated during the specified time frame that also match
any additional filter criteria specified. The XML_STRING value shows
the contents of the actual IBM Sterling Control Center
Monitor event. From these values, you are able to determine the
parameters necessary for your rule to be triggered as expected.
For
example, say that you wanted to write a rule to be triggered when
a Sterling Connect:Direct® server stops.
- First, while IBM Sterling Control Center
Monitor is monitoring a server, stop the server.
- Second, create a Database Events Report over the time frame
the server was stopped.
- Locate the event generated by the server down condition
in the report.
From this event, you can see that when
a server goes down, the message ID is CCTR034E.
- You can use this information to write a server down rule.
In creating the server down rule, specify a parameter with a Key of
Message ID, an Operator of Matches, and Value of CCTR034E.