Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Manager i10.62

Administer > Management Packs > Management Pack for OMi Server Self-Monitoring

Management Pack for OMi Server Self-Monitoring

The OMi Server Self-Monitoring out-of-the-box management pack enables monitoring the health of the OMi deployment. It contains a management template and aspects for monitoring the availability, status, and performance of individual OMi components and processes.

The OMi Server Self-Monitoring management pack is uploaded with the OMi Content Pack. The OMi self-monitoring functionality becomes active immediately after the OMi installation. As soon as the OMi servers are started and the OMi Content Pack is uploaded, the OMi Server Self-Monitoring management template is assigned to the OMi Deployment view using an automatic assignment rule.

For more information on automatic assignment rules, see Automatic Assignment Rules.

Learn more

Management pack components

The OMi Server Self-Monitoring management pack includes the OMi Server Self-Monitoring management template containing the following aspects:

OMi Data Processing Server monitoring

This aspect includes the following policy templates:

CI Type	Policy Template	Policy Description	Policy Type
OMi Data Processing Server	OMi Bus Logfile	Monitors the log file of the JMS bus`bus.log` located in the `<OMi_HOME>/log/bus` directory. All log file entries with the severity `ERROR` create an OMi event.	Logfile Entry
	OMi CI Resolver Logfile	Monitors the CI Resolver log file `opr-ciresolver.log` located in the `<OMi_HOME>/log/opr-backend` directory. All log file entries with the severity `ERROR` create an OMi event.	Logfile Entry
	OMi Marble Logfiles	Monitors the following OMi log files for the Marble Status Calculation: `<OMi_HOME>/log/marble_loader/loader.all.log` `<OMi_HOME>/log/marble_matcher/marble.matcher.all.log` `<OMi_HOME>/log/marble_supervisor/marble.supervisor.all.log` All log file entries with the severity `ERROR` create an OMi event.	Logfile Entry
	OMi Nanny Logfile	Monitors the OMi Nanny process log file `nannyStatus.log` located in the `<OMi_HOME>/log/supervisor` directory. (The Nanny process is responsible for all processes running on an OMi system. If an OMi process fails, Nanny restarts it automatically and records the information to a log file.)	Logfile Entry
	OMi Scripting Host Logfile	Monitors the OMi scripting host log files `opr-scripting-host.log` and `scripts.log` located in the `<OMi_HOME>/log/opr-scripting-host/` directory. All log file entries with the severity `ERROR` create an OMi event.	Logfile Entry
	OMi Server Processes (Linux)	Monitors the Linux Server processes.	Service/Process Monitoring
	OMi Server Processes (Windows)	Monitors the Windows Server processes.	Service/Process Monitoring
	OMi_BusMonitor	Monitors the OMi JMS bus. See also JMS Bus monitoring.	Measurement Threshold

OMi Gateway Server monitoring

This aspect includes the following policy templates:

CI Type	Policy Template	Policy Description	Policy Type
OMi Gateway Server	OMi Event Receiver Logfile	Monitors the Event Receiver log file `opr-gateway.log` located in the `<OMi_HOME>/log/wde` directory. All log file entries with the severity `ERROR` create an OMi event.	Logfile Entry
	OMi Nanny Logfile	Monitors the OMi Nanny process log file `nannyStatus.log` located in the `<OMi_HOME>/log/supervisor` directory.	Logfile Entry
	OMi Scripting Host Logfile	Monitors the OMi scripting host log files `opr-scripting-host.log` and `scripts.log` located in the `<OMi_HOME>/log/opr-scripting-host/` directory. All log file entries with the severity `ERROR` create an OMi event.	Logfile Entry
	OMi Server Processes (Linux)	Monitors the Linux Server processes.	Service/Process Monitoring
	OMi Server Processes (Windows)	Monitors the Windows Server processes.	Service/Process Monitoring
	OMi_CertMonitor	Monitors the validity of the OMi web server certificate. See also Certificate Expiration.	Measurement Threshold

Note The OMi Server Self-Monitoring management pack also includes the Space Availability and Disk IOPS aspect that is part of the Infrastructure management pack. This aspect is designed for monitoring the disk IO operations and space utilization of the system.

JMS Bus monitoring

The JMS bus is the central OMi component that is used to establish communication between OMi components on different OMi systems. The following areas of the JMS bus performance are monitored on the data processing server:

The time of the last event processed on the data processing server.
The size of JMS bus queues on all systems.

The error is reported if the following occurs:

The time of the last processed event does not change for a number of intervals and at least one of JMS bus queues has a size bigger than zero.
The size of the JMS bus queue is bigger than the value specified as the threshold limit.

The information is stored in the _MessageBroker.log file located in the <OMi_HOME>/log/bus directory. Log file entries with the severity ERROR create an OMi event. However, problems with the JMS bus can result in situations when no events are sent to the Event Browser, because the JMS bus itself is used for the event transmission.

Therefore, the OMI_BusMonitor policy template monitors whether the JMS bus still processes the available events. If it detects that the events are available but they are not being processed, it first attempts to run an automatic action to solve the problem. If the problem persists, an email notification is sent to inform the user about the problem.

As a prerequisite for receiving notifications, you must configure an SMTP server for email notifications in the Infrastructure Settings Manager and then define the email address in the Address to send the notification email for a JMS Bus error parameter for the OMi Server Self-Monitoring automatic assignment rule.

Task

How to configure an email notification for the JMS bus component

To configure email notifications for the JMS bus errors, proceed as follows:

Open the Infrastructure Settings Manager:

Administration > Setup and Maintenance > Infrastructure Settings

Alternatively, click Infrastructure Settings.
Click the Foundations context and then select Platform Administration from the drop-down box.
In Platform Administration - Alerts E-Mail Settings, configure the SMTP server for the email notification by modifying the SMTP server (Windows only) setting. Enter the SMTP server name in the Field value of the Edit Setting dialog.
Open the Automatic Assignment Rules Manager:

Administration > Monitoring > Automatic Assignment Rules

Alternatively, click Automatic Assignment Rules.
In the Auto-Assignment Rules pane, select the OMi Server Self-Monitoring automatic assignment rule and click the button. The Edit Auto-Assignment Rule dialog opens.
Double-click the parameter Address to send the notification email for a JMS Bus error and enter the email address in the Value field of the Edit Parameter dialog. Click OK.

Send Help Center feedback