-
Log on to the computer with an account that is a member of the Operations Manager Administrators user role or Operations Manager Authors user role for the Operations Manager 2007 Management Group.
-
In the Operations Console, click the Authoring button.
Note |
|---|
|
When you run the Operations Console on a computer that is not a Management Server, the Connect To Server dialog box will display. In the Server name text box, type the name of the Operations Manager 2007 Management Server that you want the Operations Console to connect to.
|
-
In the Authoring pane, expand Authoring, expand Management Pack Objects, and then click Monitors.
-
In the toolbar, click Scope.
-
In the Scope Management Packs Objects by target(s) dialog box, in the Look for text box, type Windows Computer, select the Windows Computer target check box, and then click OK.
-
In the Monitors pane, expand Windows Computer, expand Entity Health, right-click Availability, point to Create a monitor, and then click Unit Monitor.
-
In the Create Monitor Wizard, on the Select a Monitor Type page, expand Log Files, expand Text Log, expand Simple Event Detection, click Event Reset, and then click Next.
-
On the General Properties page, in the Name box, type a name for the unit monitor, and then as an option, you can type a description.
-
Click the Parent monitor arrow, select the appropriate parent monitor, and then click Next.
-
On the Application Log Data Source page (for the First Generic Log), under Define the application log data source, in the Directory text box, type a path to where the log files are located, for example, C:\logfiles.
-
In the Pattern text box, type a pattern string to select log files, for example application.log. Select UTF8 if applicable, and then click Next.
-
On the Build Event Expression page (for the Build First Expression),click Insert and then do the following:
-
Under Parameter Name (on the left), type Params/Param[1].
Note |
|---|
| The entry Params/Param[1] is the only option available for this field in this monitor. |
-
Under Operator, click the pull down menu and select an operator, for example Contains.
-
Under Value enter the text that this monitor should trigger on as found in the log file, for example error.
-
Click Next.
-
On the Application Log Data Source page (for the Second Generic Log), under Define the application log data source, in the Directory text box, type a path to where the log files are located, typically the same path you entered in step 10, for example C:\logfiles.
-
In the Pattern text box, type a pattern string to select log files, typically the same log file you entered in step 11, for example application.log. Select UTF8 if applicable, and then click Next.
-
On the Build Event Expression page (for the Build Second Generic Log), click Insert and then do the following:
-
In the Parameter Name text box, type Params/Param[1].
Note |
|---|
| The entry Params/Param[1] is the only option available for this field in this monitor. |
-
Under Operator, click the pull down menu and select an operator, for example Contains.
-
Under Value enter the text that this monitor should trigger on as found in the log file, for example success.
-
Click Next.
-
On the Configure Health page:
-
In the SecondEventRaised row, select the name in the Operational State column and type a display name for this condition. Click the Health State column, and then use the drop-down box to select Critical, Warning, or Healthy.
-
In the FirstEventRaised row, select the name in the Operational State column and type a display name for this condition. Click the Health State column, and then use the drop-down box to select Critical, Warning, or Healthy.
Note |
|---|
|
One of the two events must be configured to set the health state to Healthy.
|
-
Click Next.
-
On the Configure Alerts page, use the default settings or select the Generate alerts for this monitor check box to set custom alert properties, and then click Create.