The agent discovers some of the objects to monitor. You can manually add other objects, such as files, scripts or processes, and specify the details so that the agent can monitor them.
The Monitor OS Object action only appears in the Actions menu of an object that can be a parent object.
Procedure
- In the left pane of vRealize Operations Manager, select the agent adapter object that is to be the parent under which you are creating an OS object.
- Select .
A list of parent object context-sensitive objects appear in the menu.
- Choose one of the following options.
- Specify a display name for the OS object.
- Enter the appropriate values in the other text boxes.
The options in the menu are filtered according to the OS object type that you select.
Some text boxes might display default values, which you can overwrite if necessary. Note the following information about default values.
Option |
Value |
Process |
Supply the PTQL query in the form: Class.Attribute.operator=value . For example, Pid.PidFile.eq=/var/run/sshd.pid . Where:
Class is the name of the Sigar class without the Proc prefix.
Attribute is an attribute of the given Class, index into an array or key in a Map class.
operator is one of the following (for String values):
eq Equal to value
ne Not Equal to value
ew Ends with value
sw Starts with value
ct Contains value (substring)
re Regular expression value matches
Delimit queries with a comma. |
Windows Service |
Monitor an application that runs as a service under Windows. To configure it, you supply its Service Name in Windows. To determine the Service Name:
- Select Run from the Windows Start menu.
- Type
services.msc in the run dialog box and click OK.
- In the list of services displayed, right-click the service to monitor and choose Properties.
- Locate the Service Name on the General tab.
|
Script |
Configure vRealize Operations Manager to periodically run a script that collects a system or application metric. |
- Click OK.
You cannot click
OK until you enter values for all the mandatory text boxes.
Results
The OS object appears under its parent object and monitoring begins.
Caution: If you enter invalid details when you create an OS object, the object is created but the agent cannot discover it, and metrics are not collected.