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 > Monitoring > Policy Templates > Configure Measurement Threshold Policies

Configure Measurement Threshold Policies

Measurement threshold policies enable you to monitor performance metrics from various sources. You can configure policies to create events and launch commands whenever a performance metric crosses a threshold that you specify.

To access

You can create or edit a Measurement Threshold policy using the Measurement Threshold policy editor, which you can open in the following ways.

You can create or edit a Perl Script policy using the Perl Script policy editor, which you can open in the following ways.

To open the editor from the Edit Aspect dialog box:
1. Open the Management Templates & Aspects manager:
  
  Administration > Monitoring > Management Templates & Aspects
  
  Alternatively, click Management Templates & Aspects.
2. In the Configuration Folders pane, expand the configuration folders.
3. In the Management Templates & Aspects pane, click an aspect, and then click the Edit Item button.
  
  The Edit Aspect dialog box opens.
4. Click the Policy Templates tab, and then do one of the following:
  - To add a new policy template:
    1. Click the Add Policy Templates From List button. The Add Policy Templates From List dialog box opens.
    2. Click the New Item button, and then click the Add New Policy Template or the Add New Policy Template (Raw Mode) button. The Select Type for New Policy Template dialog box opens.
    3. Select the type Measurement Threshold, and then click OK.
    4. Select the appropriate type <DataType> from Perl Script, and then click OK.
  - To edit an existing policy template, click the policy template in the list, click the button, and then click the Edit Policy Template or the Edit Policy Template (Raw Mode) button.
  The Operations Connector High Availability policy editor opens.
  
  The Measurement Threshold policy editor opens.
  
  The Perl Script policy editor opens.
To open the editor from the Policy Templates manager:
1. Open the Policy Templates manager:
  
  Administration > Monitoring > Policy Templates
  
  Alternatively, click Policy Templates.
2. In the Policy Template Groups pane, expand Policy Management > Templates grouped by type.
3. Depending on the type of data collected by the particular policy, expand Configuration, Events, Generic, Metrics, or Topology. Each policy type can be used only for a subset of the available data types.
4. Click the Measurement Threshold item, and then do one of the following:
  - To add a new policy template, in the Policy Templates pane, click the button, and then click the Add New Policy Template or the Add New Policy Template (Raw Mode) button.
    
    The New Measurement Threshold policy editor opens.
  - To edit an existing policy template, click the policy template in the Policy Templates pane, click the button, and then click the Edit Policy Template or the Edit Policy Template (Raw Mode) button.
    
    The Edit Measurement Threshold policy editor opens.
5. Click the <DataType> from Perl Script item in the appropriate folder, and then do one of the following:
  - To add a new policy template, in the Policy Templates pane, click the button, and then click the Add New Policy Template or the Add New Policy Template (Raw Mode) button.
    
    The New <DataType> from Perl Script policy editor opens.
  - To edit an existing policy template, click the policy template in the Policy Templates pane, click the button, and then click the Edit Policy Template or the Edit Policy Template (Raw Mode) button.
    
    The Edit <DataType> from Perl Script policy editor opens.

Learn More

Tasks

How to Create a Measurement Threshold Policy

In the Measurement Threshold Policy Editor, in the Properties page, type a Name for the policy.

Optional. Provide a description of the policy (Description), select the instrumentation that will be deployed with the policy onto the host system where the agent is running (Instrumentation), and select the operating systems with which the policy is compatible (OS Types).

For more information, see Properties Page.
In the Source page, define the sources that you want to monitor.
1. Click Add Source and select one of the following source types:
  - Add Embedded Performance Component Source: Use this option if you want to monitor performance counter and instance data collected by the Embedded Performance (Coda) component.
  - Add External Source: Use this option if you want to monitor data sent from an external program (the opcmon command-line tool, for example). HPE Operations Agent does not poll the external program but waits for values to arrive.
  - Add Management Information Base Source: Use this option if you want to monitor data stored in a Management Information Base (MIB).
  - Add Program Source: Use this option if you want to monitor data sent from an external program. HPE Operations Agent runs the external program at each polling interval.
  - Add Real Time Performance Measurement Source: Use this option if you want to monitor data gathered by the Windows performance monitor.
  - Add Windows Management Instrumentation Source: Use this option if you want to monitor data stored in the WMI database.
2. Type a Short Name and optionally a Description of the source. These labels can help you recognize the value or metric for the threshold source.
3. Optional. Click Store in Coda to configure the policy to store the collected data in the Embedded Performance Component (Coda). Other users can then consume the data from Coda (for example, to create graphs in the Performance Dashboard).
  
  You can enter a Data Source, Object and optionally a Metric of your own invention here. The policy will create them in the Embedded Performance Component (Coda) and will store the data from the policy's source each polling interval.
4. Optional. Click and add another source to the policy. You can add as many sources as required.
5. Accept the default Polling Interval of five minutes or set another interval.
For more details, see Source Page.
Optional. In the Defaults page, set default attributes for all events that the policy sends.

The event defaults only affect new rules. You can override the defaults for individual rules.

Note You can set defaults for only a subset of event attributes. You can set the other event attributes within individual rules.

For more details, see Event Attributes Tab, Instructions Tab, and Advanced Tab.
In the Processing page, set options that determine how the collected data is processed by the policy.
1. Select how you want to set the threshold level:
  - Minimum: Sets a minimum threshold level under which the monitored value must drop for a rule to match.
  - Maximum: Sets a maximum threshold level that the monitored value must exceed for a rule to match.
  - Perl Script: Configures the policy to use a Perl script that evaluates the sources you are monitoring and determines the threshold limit.
  - VB Script: Configures the policy to use a VB script that evaluates the sources you are monitoring and determines the threshold limit.
2. Optional. Click Use Instance Filter to enable instance filters for the policy. Switching to instance filters cannot be reverted.
3. Optional. If you are using scripts to set and evaluate the threshold level, you can choose how the policy processes multiple instances of the value being measured.
  
  Click Process each instance separately if you want each instance to be processed by the policy separately. For example, if the policy monitors each CPU in a multiple CPU server, and the activity of all CPUs exceeds the threshold, an event will be generated for each CPU.
  
  Alternatively, accept the default, which is to process all instances once.
4. Optional. Click Show only newest event in event browser to ensure that only the most current status of a threshold is shown in the Event Browser.
  
  This option automatically inserts values in the Event Key and Close Events with Keys fields, which cause a threshold event to close all events that were created by the same policy and that have the same node and instance.
For more details, see Processing Page.
If instance filters are not enabled, define one or more threshold rules in the Rules page.
1. Click Create New Threshold to add a new threshold rule.
2. In Threshold Definition, use the Definition tab to define the threshold value that you want to evaluate against the monitored value:
  1. In Threshold Level Description, type a description of the rule to help you identify it.
  2. Define the threshold limit:
    - Minimum thresholds: <= (less than or equal to): Set the value that triggers an event if the monitored value is equal or lower.
    - Maximum thresholds: >= (greater than or equal to): Set the value that triggers an event if the monitored value is equal or higher.
    - Scripts: Write a script that evaluates the sources you are monitoring and sets the Rule Object to either TRUE or FALSE.
      
      The script should use the short names and the policy objects to access the value for each source, and should perform some calculation to determine if a threshold has been crossed. The script should set the Rule Object to TRUE if the threshold has been crossed or FALSE if it has not been crossed.
      
      When the policy is deployed, the script will evaluate the sources and sets the rule object to TRUE or FALSE after each polling interval. If rule object is set to TRUE, the policy will carry out the start, continue, or end actions depending on how long the threshold has been crossed. You can also use the script to send events or run commands directly if you require more flexibility than the start, continue, and end actions provide.
  3. Optional. Click Ignore single short-term peaks occurring within: and set a value that is a multiple of the policy's polling interval. If the duration is set to 0 or the box is left empty, an alarm is generated as soon as HPE Operations Agent detects that the threshold has been equaled or crossed.
  4. Optional. Click Specify a special reset value for the threshold level and set the reset value. For minimum and maximum rules, type the value in the field; for scripts write a script that evaluates the sources and determines the reset value. Alternatively, use the same value as the threshold limit.
  For more details, see Threshold Rules—Definition Tab.
3. Optional. Click Actions and indicate what the policy should do after evaluating the threshold level. The policy can send an event, start a command, prepare a command for the operator to start, or any combination or none of these actions.
  - Start actions are always carried out.
  - Continue actions are optional; they are carried out at each polling interval if the start action of the rule was carried out at a previous polling interval, and the reset value is not reached. To configure continue actions, click Define special "Continue Actions".
  - End actions are also optional; they are carried out after the threshold crosses the reset value, only if the start action for that rule was carried out. To configure end actions, click Start the specified "End Actions".
  Complete the following steps to configure start, continue, and end actions:
  1. Optional. Click Start Actions and use the tabs to configure the event that the agent sends when the threshold is crossed for the first time. If you do not configure details of the event, the event defaults are used.
  2. Optional. Click Continue Actions and use the tabs to configure the event that the agent sends at each polling interval if the reset value is not reached. If you do not configure details of the event, the event defaults are used.
  3. Optional. Click End Actions and use the tabs to configure the event that the agent sends after the threshold crosses the reset value. If you do not configure details of the event, the event defaults are used.
  For more details, see Threshold Rules—Actions Tab.
If instance filters are enabled, define one or more instance rules in the Rules page.
1. Click Create New Rule, and then choose one of the following rule types:
  - Evaluate thresholds if matched. If the instance matches the condition, all thresholds are evaluated and an event is sent to OMi.
  - Stop evaluation if matched. If the instance matches the condition, the agent stops processing and does not send an event to OMi.
  - Stop evaluation if not matched. If the instance does not match the condition, the agent stops processing and does not send an event to OMi.
  For more details, see Instance Rules—Overview.
2. In Instance Rule Definition, use the Definition tab to define the condition that the instance must match:
  1. Provide a Rule Description (for example, matches the C drive).
  2. Optional. Check the Rule Type. This is the type you selected in the previous step. If necessary, select another type from the drop-down list.
  3. Specify the instances that you want to monitor:
    - Minimum and maximum:
      
      In Object Name, type a pattern matching string that will match the instance (or instances) for which you want to write specific rules.
    - Scripts:
      
      Click Filter using object name pattern if you want to use a pattern matching string to match the instance (or instances) for which you want to write specific rules.
      
      Alternatively, click Filter using script and type a VB Script or Perl Script that filters the object instances.
      
      For a VB Script threshold, set Rule.Status = True if the object instance matches the condition. Otherwise set Rule.Status = False.
      
      For a Perl Script threshold, set $Rule->Status(TRUE); if the object instance matches the condition. Otherwise set $Rule->Status(FALSE);.
  For more details, see Instance Rules—Definition.
3. Optional. If you are creating a rule of the type 'evaluate thresholds if matched', create the threshold values that you want to evaluate against the instance values.
  
  In Instance Rule Definition, click Thresholds, and then click Create New Threshold to add a new threshold rule.
4. In Threshold Definition, use the Definition tab to define the threshold value that you want to evaluate against the instance value:
  1. In Threshold Level Description, type a description of the rule to help you identify it.
  2. Define the threshold limit:
    - Minimum thresholds: <= (less than or equal to): Set the value that triggers an event if the monitored value is equal or lower.
    - Maximum thresholds: >= (greater than or equal to): Set the value that triggers an event if the monitored value is equal or higher.
    - Scripts: Write a script that evaluates the sources you are monitoring and sets the Rule Object to either TRUE or FALSE.
      
      The script should use the short names and the policy objects to access the value for each source, and should perform some calculation to determine if a threshold has been crossed. The script should set the Rule Object to TRUE if the threshold has been crossed or FALSE if it has not been crossed.
      
      When the policy is deployed, the script will evaluate the sources and sets the rule object to TRUE or FALSE after each polling interval. If rule object is set to TRUE, the policy will carry out the start, continue, or end actions depending on how long the threshold has been crossed. You can also use the script to send messages or execute commands directly if you require more flexibility than the start, continue, and end actions provide.
  3. Optional. Click Ignore single short-term peaks occurring within: and set a value that is a multiple of the policy's polling interval. If the duration is set to 0 or the box is left empty, an alarm is generated as soon as HPE Operations Agent detects that the threshold has been equaled or crossed.
  4. Optional. Click Specify a special reset value for the threshold level and set the reset value. For minimum and maximum rules, type the value in the field; for scripts write a script that evaluates the sources and determines the reset value. Alternatively, use the same value as the threshold limit.
  For more details, see Threshold Rules—Definition Tab.
5. Optional. Click Actions and indicate what the policy should do after evaluating the threshold level. The policy can send an event, start a command, prepare a command for the operator to start, or any combination or none of these actions.
  - Start actions are always carried out.
  - Continue actions are optional; they are carried out at each polling interval if the start action of the rule was carried out at a previous polling interval, and the reset value is not reached. To configure continue actions, click Define special "Continue Actions".
  - End actions are also optional; they are carried out after the threshold crosses the reset value, only if the start action for that rule was carried out. To configure end actions, click Start the specified "End Actions".
  Complete the following steps to configure start, continue, and end actions:
  1. Optional. Click Start Actions and use the tabs to configure the event that the agent sends when the threshold is crossed for the first time. If you do not configure details of the event, the event defaults are used.
  2. Optional. Click Continue Actions and use the tabs to configure the event that the agent sends at each polling interval if the reset value is not reached. If you do not configure details of the event, the event defaults are used.
  3. Optional. Click End Actions and use the tabs to configure the event that the agent sends after the threshold crosses the reset value. If you do not configure details of the event, the event defaults are used.
  For more details, see Threshold Rules—Actions Tab.
6. Repeat for each object instance.
Optional. In the Options page, configure options for local event logs, unmatched events, and pattern matching.

For more details, see Options Page.
Click Save and Close to save the policy template and exit the wizard.

UI Reference

User interface elements are described below (listed alphabetically):

Actions Tab

UI Element	Description
Automatic command Automatic command that runs when the rule is matched.
Command	Command and parameters to run when the command is started for this event. The command runs on the node you specify in the Node field. If the command contains spaces, enclose it in quotation marks. Commands that are internal to the Windows command shell (for example `echo` or `move`), must be preceded by `cmd /c`.
Non Agent User	By default, the command runs as the agent user (`$AGENT_USER`). Alternatively, select Non Agent User and specify a user account and password that exists on the node: Username. Runs the command under the specified user account. The account must exist on the node. Password. Password of the specified user account. Enable Policy Parameter in password field. Enables you to enter a variable in the Password field, for example `%%password%%`. A corresponding policy parameter should exist in the Policy Parameters tab.
Node	Name of the node on which the command will be started. You can also use the variable `<$MSG_NODE_NAME>` to configure reusable policies for replicated sites.
Append output of command as annotation to the event	Adds an annotation to the event when the command completes. The annotation contains the start time, output, exit value, and finish time of the command. If a command fails, an annotation is provided even if this item is not selected.
Close the event when the command is successful	Closes the event automatically if the command is successful.
Send event immediately	Sends an event to the OMi server as soon as a local automatic command starts on the node. This is the default setting.
Wait until local command completes and then	Options that can help to reduce the amount of unnecessary network traffic to the OMi server. For example, if an automatic command solves the problem that generated the event, you may choose not to inform the OMi server. Send the event Send the event if the local command fails Send the event only if the local command is successful
Operator-initiated command Operator-initiated command that is attached to the event that the rule sends to OMi. This command can be started by the OMi user from the Event Browser. The command might be a script that requires user input to solve the problem, or instructions that appear in a Web browser.
Command	Command and parameters to run when the command is started for this event. The command runs on the node specified in the Node field. If the command contains spaces, enclose it in quotation marks. Commands that are internal to the Windows command shell (for example `echo` or `move`), must be preceded by `cmd /c`.
Non Agent User	By default, the command runs as the agent user ($AGENT_USER). Alternatively, select Non Agent User and specify a user account and password that exists on the node: Username. Runs the command under the specified user account. The account must exist on the node. Password. Password of the specified user account. Enable policy parameter in Password field. Enables you to enter a variable in the Password field, for example `%%password%%`. A corresponding policy parameter should exist in the Policy Parameters tab.
Node	Name of the node on which the command will be started. You can also use the variable `<$MSG_NODE_NAME>` to configure reusable policies for replicated sites.
Append output of command as annotation to the event	Adds an annotation to the event when the command completes. The annotation contains the start time, output, exit value, and finish time of the command. If a command fails, an annotation is provided even if this item is not selected.
Close the event when the command is successful	Closes the event automatically if the command is successful.

Advanced Tab

Note In the default event attributes, you cannot set the following attributes:

Event Drilldown URL
Type

You can set these event attributes within individual rules.

UI Element	Description
Event Drilldown
Event Drilldown URL	URL of the event in a third-party system. This is the complete path of the URL, and includes the FQDN (fully qualified domain name) of the computer that hosts the third-party system, the communication port, and the root URL path (for example, `http://nnmi.example.com:8004/nnm/launch?cmd=showForm&objtype =Incident&objuuid=$OPC_CUSTOM[nnm.incident.uuid]&menus=true`). Event drilldown information enables OMi users to launch the user interface of the third-party system in the context of an event. Tip To drill down to a specific event in the third-party system, add the source event ID to the URL.
OM Attributes
Application	Application that caused the event to occur. Unlike the Related CI attribute, which is a direct relationship to a CI in the RTSM, the application attribute is a simple string-type attribute (for example, Oracle and OS).
Object	Device such as a computer, printer, or modem. Unlike the Related CI attribute, which is a direct relationship to a CI in the RTSM, the object attribute is a simple string-type attribute (for example, `C:`, and `/dev/spool`).
Type	String used to organize different types of events within an event category or subcategory (for example, users or applications, accounts and security).
HPOM Service ID	ID of the service associated with the event. A service ID is a unique identifier for a service and can be used in OMi to identify the node and CI associated with the event.
Agent MSI
Enable Agent MSI	The message stream interface (MSI) allows external applications to interact with the internal event flow of the agent. The external application can be a read-write application, for example, an event processing program that can read events, modify attributes, and generate new events for retransmission to the server. The application could also read events, or send its own events. Divert events. Divert an event to the MSI instead of to the server when an event is requested by an external application. Copy events. Send the event to the server, and a copy of the event to the MSI. If the agent MSI is enabled in the event defaults, you can choose to apply them to or override them for this rule: Use default settings for Agent MSI. Applies the agent MSI settings configured in the event defaults to this rule. Override default settings for Agent MSI: Enables you to configure specific agent MSI settings for this policy rule.

Custom Attributes Tab

UI Element	Description
	Create New Custom Attribute: Creates a new custom attribute with the default name CA_n. To rename the custom attribute, double-click the name to select it and type the new name.
	Delete Custom Attribute: Deletes an existing custom attribute.
Name	The name of the custom attribute. The name is case-insensitive. Custom attributes are additional attributes that contain any information that is meaningful to you. For example, you might add a company name, contact information, or a city location to an event. You can have more than one custom attribute attached to a single event. The following custom attribute names cannot be used because they are reserved for internal use: `Description` `EtiHint` `HP_OPR_SAAS_CUSTOMER_ID` `NoDuplicateSuppression` `RelatedCiHint` `SourceCiHint` `SourcedFromExternalId` `SourcedFromExternalUrl` `SubCategory` `SubCiHint`
Value	Value of the custom attribute.

Event Attributes Tab

Note In the default event attributes, you can set only the following attributes:

Severity
Category
Node

You can set the other event attributes within individual rules.

UI Element	Description
Title	Brief description of the nature of the event.
Description	Detailed description of the event.
Severity	Severity assigned to the event. Accept the severity that is set in the event defaults or choose a specific event severity: Critical, Major, Minor, Warning, Normal.
Category	Name of the logical group to which the event belongs (for example, Database, Security, or Network). The event category is similar in concept to the HP Operations Manager message group.
Subcategory	Name of the logical subgroup (category) to which the event belongs (for example, Oracle (database), Accounts (security), or Routers (network)).
ETI	Contains the event type indicator (ETI) resolution hint, which OMi uses to associate the event with an ETI and for event correlation. Use the format `<ETI name>:<ETI state>:<metric value>`. Specify the name of the indicator (for example, CPULoad), the indicator state (for example, High), and, optionally, the metric value (for example, 80). When OMi receives an event with an ETI resolution hint of CPULoad:High, and the ETI and state exist, the Event Type Indicator attribute is set to CPULoad:High in the event. The metric value is optional and serves informational purposes only.
Node	Name of the system where the event occurred (for example, node.example.com).
Related CI	Contains the CI that is related to the metric (for example, oraclesid01@@node.example.com or C:@@server.example.com). Use the format `<CI 1>:<CI 2>:...:<CI n>@@<hostname>`. Best practices for related CIs It is necessary to differentiate between CIs that have a Composition relationship to a node, and those that do not have such a relationship: For “hosted on” CIs `<key attribute 1>:<key attribute 2>:<key attribute n>@@<hostname>` Typically, a “hosted on” CI is a sub-type of “Running Software”. For example, a CI of type `websphereas` has a Composition relationship to a node. For virtual CIs `<key attribute 1>:<key attribute 2>:<key attribute n>` A virtual CI does not have a strong containment relationship (Composition relationship) to node. An example of a typical virtual CI type is cluster. This CI type does not have a strong containment relationship to a node. Tip If you have problems resolving non-hosted CIs, provide the RTSM ID of the desired CI by using the format `UCMDB:<ci_uuid>`. For more information about CI resolution in OMi, see the OMi Help.
Sub Component	Information used to identify a subcomponent of a CI. This CI subcomponent is used to calculate an aggregated status within OMi's Service Health for selected CIs. If an HI is populated by events from multiple components, you can specify a component name in this field in order to ensure the correct calculation of the HI state. For example, if you have a Computer CI with two CPUs, `cpu #1` and `cpu #2`, events from both CPUs will be sent to the same `CPU Load` HI. By default, the events will override each other and create an incorrect HI state. To prevent this, you can populate Sub Component with values `"cpu #1"` and `"cpu #2"` which will cause the HI state to be calculated as an aggregated state between the two events.
Source CI	Contains the source related CI. For example, type the name and instance of the OMi server that provides events (for example, OMi@@mgmt.example.com). If you enter a source related CI, OMi tries to find the corresponding CI in the RTSM.
Source Event ID	Reserved for future use.
Send with closed status (For the Open Message Interface, SNMP Interceptor, and Scheduled Task policies)	Sets the event's lifecycle status to Closed before sending it to OMi.

Event Correlation Tab

Note In the default event attributes, you cannot set the following attributes:

Close Events with Key
Suppress Deduplication on Server

You can set these event attributes within individual rules.

UI Element	Description
Event Key	An identifier used to identify duplicates and for Close Events with Key.

Indicators Tab

UI Element	Description
	Refresh. Loads the configured indicators from the OMi server. Note Loading indicators from the OMi server may take a few seconds.
<Search …>	Entered search string is used to search the indicators and highlight only the indicators containing the specified string. To search for indicators with specific text strings in the name, type the string in the <Search …> field and click the button. The first matching indicator is selected in the list of rules. Click the and buttons to move to the previous and next matching indicator.
<Indicators>	Hierarchy of configuration item types with associated health indicators (HIs), which are applicable for the event integration only, and event type indicators (ETIs). To insert an indicator with a state in a policy, drag and drop the indicator from the Indicators tab to the relevant field in the policy.

UI Element

Description

Refresh. Loads the configured indicators from the OMi server.

Note Loading indicators from the OMi server may take a few seconds.

Entered search string is used to search the indicators and highlight only the indicators containing the specified string.

To search for indicators with specific text strings in the name, type the string in the <Search …> field and click the button. The first matching indicator is selected in the list of rules. Click the and buttons to move to the previous and next matching indicator.

Hierarchy of configuration item types with associated health indicators (HIs), which are applicable for the event integration only, and event type indicators (ETIs). To insert an indicator with a state in a policy, drag and drop the indicator from the Indicators tab to the relevant field in the policy.

Instance Rules—Overview

UI Element	Description
	Create New Rule: Provides the following options: Evaluate thresholds if matched. If the instance matches the condition, all thresholds are evaluated and an event is sent to OMi. Stop evaluation if matched. If the instance matches the condition, the agent stops processing and does not send an event to OMi. Stop evaluation if not matched. If the instance does not match the condition, the agent stops processing and does not send an event to OMi.
	Copy Rule: Copies the selected instance rule. You can then rewrite the description of the copied rule and edit the rule.
	Delete Item: Deletes the selected instance rule.
	Move Up. Moves the selected instance rule higher in the rule order.
	Move Down. Moves the selected instance rule lower in the rule order.
<Move to>	Entered number is used to select the instance rule with that sequence number in the list of rules. To select a specific instance rule in the rule list, type the rule's sequence number in the <Move to> field and click the button.
<Search Thresholds>	Entered search string is used to search the instance rule descriptions and highlight only the rules containing the specified string. To search for instance rules with specific text strings in the rule description, type the string in the <Search Rules> field and click the button. The first matching rule is selected in the list of rules. Click the and buttons to move the previous and next matching rule.
	Activate/Deactivate Threshold Filter. Activates and deactivates the instance rule filter.
Seq.	Sequence number of the instance rules. Rules are evaluated in a specific order. When one condition is matched, no additional rules are evaluated.
Rule Description	Description of the instance rule. It is good practice to use a description that helps you remember what the rule does.
Rule Type	The three rule types are: Evaluate thresholds if matched. If the monitored object matches the condition, all thresholds are evaluated and an event is sent to OMi. Stop evaluation if matched. If the monitored object matches the condition, the agent stops processing and does not send an event to OMi. Stop evaluation if not matched. If the monitored object does not match the condition, the agent stops processing and does not send an event to OMi.
Amount Thresholds	The number of thresholds configured for the selected instance rule.

Instance Rules—Definition

UI Element	Description
Rule Description	This is a name you give to the rule to help you identify it. This name is visible in the rules list.
Rule Type	The three rule types are: Evaluate thresholds if matched. If the monitored object matches the condition, all thresholds are evaluated and an event is sent to OMi. Stop evaluation. Cancels evaluation of the remaining rules. Stop evaluation if matched. If the monitored object matches the condition, the agent stops processing and does not send an event to OMi. Stop evaluation if not matched. If the monitored object does not match the condition, the agent stops processing and does not send an event to OMi.
Object name	Minimum and maximum processing rules only: Type a pattern matching string that will match the instance (or instances) for which you want to write specific rules.
Filter using object name pattern	Script processing only: Type a pattern matching string that will match the instance (or instances) for which you want to write specific rules.
Filter using script	Script processing only: Type a VB Script or Perl Script that filters the object instances: For a VB Script threshold, set `Rule.Status = True` if the object instance matches the condition. Otherwise set `Rule.Status = False`. For a Perl Script threshold, set `$Rule->Status(TRUE);` if the object instance matches the condition. Otherwise set `$Rule->Status(FALSE);`.

Instance Rules—Thresholds

UI Element	Description
	Create New Threshold: Adds an empty threshold rule to the list for you to edit.
	Copy Threshold: Copies the selected threshold rule. You can then rewrite the description of the copied rule and edit the rule.
	Delete Item: Deletes the selected threshold rule.
	Move Up. Moves the selected threshold rule higher in the rule order.
	Move Down. Moves the selected threshold rule lower in the rule order.
<Move to>	Entered number is used to select the threshold rule with that sequence number in the list of rules. To select a specific threshold rule in the rule list, type the rule's sequence number in the <Move to> field and click the button.
<Search Thresholds>	Entered search string is used to search the threshold rule descriptions and highlight only the rules containing the specified string. To search for threshold rules with specific text strings in the rule description, type the string in the <Search Thresholds> field and click the button. The first matching rule is selected in the list of rules. Click the and buttons to move the previous and next matching rule.
	Activate/Deactivate Threshold Filter. Activates and deactivates the threshold rule filter.
Seq.	Sequence number of the threshold rules. Rules are evaluated in a specific order. When one condition is matched, no additional rules are evaluated.
Threshold Level Description	Description of the threshold rule. It is good practice to use a description that helps you remember what the rule does.

Instructions Tab

Specify if you want the instructions to accompany the event.

Events generated by a policy can include instructions that explain what to do when the event is generated. This instruction text can often help an operator to solve a problem when a particular type of event is received. The operator can view the instructions included with an event by checking the Event Details pane in the Event Browser. You can define default instructions for all rules in a policy. You can also override the default with different instructions for any rule.

UI Element	Description
Type	You can select one of the following options from the Type drop-down list: Use defaults. Select if you do not want to use instructions that accompany the event. Instruction Text. Select if you want to add the instruction text to accompany the event. Enter the text directly in the Instruction Text field. Note that you can type URLs in the text. The Event Browser automatically converts them into clickable hyperlinks. For example, you can add URLs of external websites, support sites, documentation repositories, troubleshooting information, and similar. To add a link, type any URL that begins with one of the following URI scheme names: `http://` `https://` `ftp://` `ftps://` `mailto:` `telnet://` `file://` You can also just type the address of any website that begins with `www.`. Instruction Text Interface. Select if you want to use the external instructions interface to generate instructions. Type the name of the external instructions interface in the Interface name field and enter Parameters that will be passed to the instruction text interface upon the instruction text retrieval (these parameters will get resolved by the agent before the message is sent to the server). In Parameters, you can enter a policy variable or a policy parameter configured for this policy template (note that you can also enter a parameter as a value in the Interface name field). Supported policy variables include (but are not limited to): `<$MSG_APPL>`: Returns the name of the application associated with the event. `<$MSG_NODE>`: Returns the IP address of the node on which the original event took place. `<$MSG_NODE_NAME>`: Returns the hostname of the node on which the original event took place (this is the hostname that the agent resolves for the node). `<$MSG_ID>`: Returns the unique identity number of the event. `<$MSG_SEV>`: Returns the default value for the event severity. `<$MSG_TEXT>`: Returns the full text of the event. A list of supported variables is available in the Policy Variables tab. For a complete list of HPOM variables and their descriptions, see the HPOM documentation.

UI Element

Description

Type

You can select one of the following options from the Type drop-down list:

Use defaults. Select if you do not want to use instructions that accompany the event.
Instruction Text. Select if you want to add the instruction text to accompany the event. Enter the text directly in the Instruction Text field.

Note that you can type URLs in the text. The Event Browser automatically converts them into clickable hyperlinks. For example, you can add URLs of external websites, support sites, documentation repositories, troubleshooting information, and similar.

To add a link, type any URL that begins with one of the following URI scheme names:
- http://
- https://
- ftp://
- ftps://
- mailto:
- telnet://
- file://
You can also just type the address of any website that begins with www..
Instruction Text Interface. Select if you want to use the external instructions interface to generate instructions. Type the name of the external instructions interface in the Interface name field and enter Parameters that will be passed to the instruction text interface upon the instruction text retrieval (these parameters will get resolved by the agent before the message is sent to the server).

In Parameters, you can enter a policy variable or a policy parameter configured for this policy template (note that you can also enter a parameter as a value in the Interface name field). Supported policy variables include (but are not limited to):
- <$MSG_APPL>: Returns the name of the application associated with the event.
- <$MSG_NODE>: Returns the IP address of the node on which the original event took place.
- <$MSG_NODE_NAME>: Returns the hostname of the node on which the original event took place (this is the hostname that the agent resolves for the node).
- <$MSG_ID>: Returns the unique identity number of the event.
- <$MSG_SEV>: Returns the default value for the event severity.
- <$MSG_TEXT>: Returns the full text of the event.
A list of supported variables is available in the Policy Variables tab. For a complete list of HPOM variables and their descriptions, see the HPOM documentation.

Options Page

UI Element

Description

Options in events policies:

Log Local Events

Defines which events, if any, are logged on the node from which they originated. These events are logged on the local node in the log file:

Windows: %OvDataDir%\log\OpC\opcmsglg

AIX, HP-UX, Linux, and Solaris: /var/opt/OV/log/OpC/opcmsglg

that match a rule and trigger an event Logs any events in the event source that match the policy rules.

that match a rule and are ignored Logs any events in the event source that are suppressed. (Suppressed events are not sent to OMi.)

that do not match any rule Logs any events that do not match any of the rules in the policy.

Unmatched Events

Send an event to OMi when the input event does not match any rule in the policy because none of the conditions apply or because the policy does not contain any rules. This ensures that unexpected events that might be important do not go unreported. By default, unmatched events are ignored.

Each policy that sends unmatched events to OMi creates an event with the default values of the policy.

Tip If you want a policy to send events only with the default values, omit all rules from the policy.

Note If several policies forward unmatched events to OMi, you could receive multiple events about a single input event.

are forwarded to OMi Server Sends unmatched events to OMi.

are forwarded to OMi Server with state 'closed' Sets the unmatched event's lifecycle status to Closed before sending it to OMi.

are ignored Ignores unmatched events.

Options in metrics policies:

Options in events and metrics policies:

Pattern Matching Options

Defines case sensitivity and field separators for all rules.

Case sensitive check Defines whether the case (uppercase or lowercase) of a text string is considered when the pattern of a rule is compared with the source data. When switched on, a match only occurs if the use of uppercase and lowercase letters is exactly the same in both the source data and the pattern. This is the default setting.

Field Separators

Defines which characters should be considered to be field separators. Field separators are used in the pattern as separator characters for the rule condition. You can define up to seven separators, including these special characters:

\n New line (NL)
\t Horizontal tab (HT)
\v Vertical tab (VT)
\b Backspace (BS)

\r Carriage return (CR)
\f Form feed (FF)
\a Alert (BEL)
\\ Backslash (\)

For example, if you wanted a backslash, an asterisk, and the letter A to define the fields in the event, you would type \\*A (with no spaces separating the characters).

If you leave this box empty, the default separators (a blank and the tab character) are used by default.

You can set case sensitivity and separator characters for individual rules in a policy by clicking the button in rule's match condition.

Apply to All

Applies the pattern matching options to all existing rules in a policy. This overwrites any modifications made to the pattern matching options in individual rules.

If you change the pattern matching options and do not click Apply to all, they only apply to all new rules in a policy.

Policy Data Page

UI Element	Description
	Load From Local File System: Click to open the Select file to upload dialog box. Use the dialog box to upload a policy file. Policy files are data files and their filenames end in `_data`.
	Save To Local File System: Click to download the policy to a policy data file on your system. You can then update the policy more comfortably in an editor of your choice. After completing your changes to the policy, upload the policy data file by clicking the Load From Local File System button. The policy editor automatically asks you to download policies that exceed 1 MB in file size.
	Check Syntax: Validates the syntax of the policy data. If the policy syntax is incorrect, the validation tool reports an error and points to the corresponding line and position of the unexpected token (for example the incorrect keyword).
<policy data>	Policy data in text form. The data uses the HPE Operations Agent policy syntax. The policy editor highlights the policy syntax. If the policy exceeds 1,000 lines, syntax highlighting is automatically disabled. If the policy exceeds 1 MB in file size, the policy editor automatically asks you to download the policy to a file.

Policy Parameters Tab

UI Element	Description
	Create Parameter: Open the Create Parameter dialog box.
	Edit Parameter: Open the Edit Parameter dialog box.
	Delete Parameter: Delete the selected parameter from the list.
	Synchronize Parameters: Check the policy template to make sure that variables in the format `%%<variable_name>%%` have corresponding parameters. Each variable should have one corresponding parameter. Also checks for unused parameters, for which no corresponding variable exists in the policy template. If any missing or unused parameters exist, the Synchronize Parameters dialog box opens. Read the summary, and then click Change or Ignore. If you click Change, the missing parameters are automatically created, and unused parameters are automatically deleted.
<Parameters>	List of parameters configured for this policy template. Parameters enable you to create policy templates that other users can easily customize. Each parameter corresponds to a variable in a policy template. A parameter gives consumers of a policy template the opportunity to specify the value of a variable, without having to modify the policy template themselves. To insert a parameter, drag the parameter from the Policy Parameters tab to any text field within a condition or an event definition in a policy template. Alternatively, type the parameter in the text box using the format `%%<variable_name>%%` (for example `%%CriticalThreshold%%`). An icon represents the type of parameter value, which can be one of the following: Enumeration (of several options) Number Password String

Policy Variables Tab

Policy Variables Tab for Database and REST Web Service Policies (Events only)

Variable	Description
`<$MSG_APPL>`	Returns the name of the application associated with the input event that caused the message. Sample output: `/usr/bin/su(1) Switch User`
`<$MSG_GEN_NODE>`	Returns the IP address of the node that sends the event. Sample output: `192.168.1.123`. Note On agents that run in an AIX Workload Partition (WPAR), `<$MSG_GEN_NODE>` returns the IP address of the global environment. To configure the agent to return the WPAR's IP address for this variable, set the parameter OPC_IP_ADDRESS in the eaagt namespace to the IP address of the WPAR.
`<$MSG_GEN_NODE_NAME>`	Returns the host name of the node that sends the event. Sample output: `node123.example.com`.
`<$MSG_GRP>`	Returns the default category of the event. Sample output: `Security`
`<$MSG_ID>`	Returns the unique identity number of the event, as generated by the the agent. Note that identity numbers are not generated for suppressed messages. Sample output: `6e998f80-a06b-71d0-012e-0f887a7c0000`
`<$MSG_NODE>`	Returns the IP address of the node on which the original event took place. Sample output: `192.168.1.123`
`<$MSG_NODE_NAME>`	Returns the name of the node on which the original event took place. This is the hostname that the agent resolves for the node. This variable is not fixed, however, and can be changed by a policy on a per-event basis.
`<$MSG_SEV>`	Returns the default value for the severity of the event. Sample output: `Normal`
`<$MSG_TEXT>`	Returns the full text of the event. Sample output: `SU 03/19 16:13 + ttyp7 bill-root`
`<$MSG_TIME_CREATED>`	Returns the time the message was created on the managed node in seconds elapsed since midnight (00:00:00), January 1, 1970, coordinated universal time. Sample output: `950008585`
`<$MSG_TYPE>`	Delivers the name set for message type.

Policy Variables Tab for XML File and Structured Log File Policies (Events only)

Variable	Description
`<$MSG_APPL>`	Returns the name of the application associated with the input event that caused the message. Sample output: `/usr/bin/su(1) Switch User`
`<$MSG_GEN_NODE>`	Returns the IP address of the node that sends the event. Sample output: `192.168.1.123`. Note On agents that run in an AIX Workload Partition (WPAR), `<$MSG_GEN_NODE>` returns the IP address of the global environment. To configure the agent to return the WPAR's IP address for this variable, set the parameter OPC_IP_ADDRESS in the eaagt namespace to the IP address of the WPAR.
`<$MSG_GEN_NODE_NAME>`	Returns the host name of the node that sends the event. Sample output: `node123.example.com`.
`<$MSG_GRP>`	Returns the default category of the event. Sample output: `Security`
`<$MSG_ID>`	Returns the unique identity number of the event, as generated by the agent. Note that identity numbers are not generated for suppressed messages. Sample output: `6e998f80-a06b-71d0-012e-0f887a7c0000`
`<$MSG_NODE>`	Returns the IP address of the node on which the original event took place. Sample output: `192.168.1.123`
`<$MSG_NODE_NAME>`	Returns the name of the node on which the original event took place. This is the hostname that the agent resolves for the node. This variable is not fixed, however, and can be changed by a policy on a per-event basis.
`<$MSG_SEV>`	Returns the default value for the severity of the event. Sample output: `Normal`
`<$MSG_TEXT>`	Returns the full text of the event. Sample output: `SU 03/19 16:13 + ttyp7 bill-root`
`<$MSG_TIME_CREATED>`	Returns the time the message was created on the managed node in seconds elapsed since midnight (00:00:00), January 1, 1970, coordinated universal time. Sample output: `950008585`
`<$MSG_TYPE>`	Delivers the name set for message type.

Policy Variables Tab for Open Message Interface, Scheduled Task, and SNMP Interceptor Policies (Events only)

Variable	Description
`<$MSG_APPL>`	Returns the name of the application associated with the input event that caused the message. Sample output: `/usr/bin/su(1) Switch User`
`<$MSG_GEN_NODE>`	Returns the IP address of the node that sends the event. Sample output: `192.168.1.123`. Note On agents that run in an AIX Workload Partition (WPAR), `<$MSG_GEN_NODE>` returns the IP address of the global environment. To configure the agent to return the WPAR's IP address for this variable, set the parameter OPC_IP_ADDRESS in the eaagt namespace to the IP address of the WPAR.
`<$MSG_GEN_NODE_NAME>`	Returns the host name of the node that sends the event. Sample output: `node123.example.com`.
`<$MSG_GRP>`	Returns the default category of the event. Sample output: `Security`
`<$MSG_ID>`	Returns the unique identity number of the event, as generated by the HPE Operations Agent. Note that identity numbers are not generated for suppressed messages. Sample output: `6e998f80-a06b-71d0-012e-0f887a7c0000`
`<$MSG_NODE>`	Returns the IP address of the node on which the original event took place. Sample output: `192.168.1.123`
`<$MSG_NODE_NAME>`	Returns the name of the node on which the original event took place. This is the hostname that the agent resolves for the node. This variable is not fixed, however, and can be changed by a policy on a per-event basis.
`<$MSG_SEV>`	Returns the default value for the severity of the event. Sample output: `Normal`
`<$MSG_TEXT>`	Returns the full text of the event. Sample output: `SU 03/19 16:13 + ttyp7 bill-root`
`<$MSG_TIME_CREATED>`	Returns the time the message was created on the managed node in seconds elapsed since midnight (00:00:00), January 1, 1970, coordinated universal time. Sample output: `950008585`
`<$MSG_TYPE>`	Delivers the name set for message type.
`<$NAME>` (Scheduled Task Only)	Returns the name of the policy that sent the event. Sample output: `cpu_util`
`<$OPTION(N)>` (Open Message Interface Only)	Returns the value of an optional variable that is set by `opcmsg` or `opcmon` (for example, `<$OPTION(A)>`, `< $OPTION(B)>`, and so on.).

Policy Variables Tab for All Policy Types (Metrics only)

Variable	Description
`<$MSG_GEN_NODE>`	Returns the IP address of the node that sends the event. Sample output: `192.168.1.123`. Note On agents that run in an AIX Workload Partition (WPAR), `<$MSG_GEN_NODE>` returns the IP address of the global environment. To configure the agent to return the WPAR's IP address for this variable, set the parameter OPC_IP_ADDRESS in the eaagt namespace to the IP address of the WPAR.
`<$MSG_GEN_NODE_NAME>`	Returns the host name of the node that sends the event. Sample output: `node123.example.com`.

Processing Page

UI Element	Description
Script Type	Minimum: Sets a minimum threshold level under which the monitored value must drop for a rule to match. Maximum: Sets a maximum threshold level that the monitored value must exceed for a rule to match. Perl Script: Configures the policy to use a Perl script that evaluates the sources you are monitoring and determines the threshold limit. VB Script: Configures the policy to use a VB script that evaluates the sources you are monitoring and determines the threshold limit. Caution A measurement threshold policy can only contain one of these types of rules. A conversion between threshold types is not always possible: Changing between minimum and maximum: rules are not deleted. Changing from minimum or maximum to VisualBasic or Perl: the rules are converted to script. Changing from VisualBasic or Perl to minimum or maximum: rules are deleted. Changing between VisualBasic and Perl: no conversion occurs, you must rewrite the script. Tip You must use a script to determine the threshold for your measurement threshold policy if the source that you choose delivers something other than a number or a Boolean value, or if you want to evaluate multiple sources. A script makes it possible for you to perform your own calculations and decide if the threshold has been crossed.
Instance Filter	Instance filters provide a way for the measurement threshold policy to apply different sets of threshold levels to different instances of the object being monitored. For example, a threshold policy that monitors disk usage will apply the same threshold to all disks, but if you specify instance filters, you can specify one set of threshold levels for disk C:, another set for disk D: and so on. Instance filters can be used with policies that evaluate the threshold based on a minimum, maximum, or scripts. Instance filters are not available for threshold policies based on the source MIB. Use Instance Filter: Enables instance filters for the policy. Switching to instance filters cannot be reverted.
Processing Options	You can choose how a policy processes multiple instances of the value being measured. For example, if a policy monitors disk space, then each disk in the monitored node is one instance, and you can choose whether to treat each disk separately or all disks as a whole. Process each instance separately: Select this option if you want each instance to be processed by the policy separately. For example, if the policy monitors each CPU in a multiple CPU server, and the activity of all CPUs exceeds the threshold, an event will be generated for each CPU. Process all instances once: This option can only be used if the threshold rules use the output of a script as the threshold (instead of minimum or maximum). Select this option if the script evaluates all instances and delivers one value to be tested by the policy. (Make sure that the scripting language that you choose is supported on the platform where you plan to distribute your policy.)
Event Correlation Settings	You may want to ensure that only the most current status of a threshold is shown in the Event Browser. The values that measurement threshold policies monitor can change rapidly. A condition that produces an error event might only exist for a short time. To prevent the Event Browser from filling up with threshold events that might not be current, you can use Show only newest event in event browser. This option automatically inserts values in the Event Key and Close Events with Keys fields, which cause a threshold event to close all events that were created by the same policy and that have the same node and instance.

Properties Page

UI Element	Description
Name	Name of the policy. You can use spaces in the name. The equal sign (=) is not allowed. The name is set when the policy is created and cannot be changed in new versions of a policy.
Description	Description of what the policy does. You might also add other notes (for example, data sources that are used).
Template ID	GUID (globally unique identifier) assigned to the policy template when it is first created.
Version ID	GUID (globally unique identifier) assigned to this version of the policy template when it is saved. Each version of a policy template has a unique ID.
Version	The current version of the policy. If you modify an existing policy, you create a new version of the policy in the database with a unique version number. By default, the minor version number increases by one automatically after you modify the policy and save it. If you want to save the policy with a specific version number, you can select the major or minor version number that you want. It is not possible to replace an existing version of a policy. However, you can delete a specific version of a policy. Note If you modify a policy template that is part of an HPE Operations Manager i Management Pack, increase the minor version number only. The next version of the Management Pack normally uses the next major version number.
Change Log	Text that describes what is new or modified in this version of the policy.
Last Modification	The date and time that the policy was saved. The date and time displays using the current time zone of the computer on which the Web browser runs. The language setting of the Web browser determines the date and time format (for example, `09/14/2010 8:16:38 AM` for English (United States)). If the Web browser and the computer on which the server run have different language settings, the language setting of the Web browser takes precedence. However, English is the default language if the Web browser is configured to use a language that is not available on the server.
Last Modified by	The name of the user active when the policy was saved.
Instrumentation	Instrumentation selected for this policy. Instrumentation consists of one or more programs (for example scripts or executable files) that some policies may require to complete a configuration or monitoring task. Instrumentation is deployed to nodes that have HPE Operations Agent installed when the policy is deployed. Instrumentations are unavailable if they are grayed out and their names end with "(Placeholder)". Upload them by using the Content Manager.
OS Types	Types of operating system with which this policy is compatible. To enable platform neutrality, you can create several platform specific variations of the same policy, and include them all in one aspect. OMi ensures that a policy is deployed only to host nodes that have the operating systems that you specify. If you leave all the OS type check boxes clear, the policy can be deployed to host nodes with any operating system.

Script API Tab

UI Element	Description
<Source Objects>	List of policy objects that can be used in VB and Perl scripts. For details, see Policy Objects for Scripts.

Source Objects Tab

UI Element	Description
<Source Objects>	List of sources that the policy monitors. You can insert the source objects in the event attribute fields using drag and drop.

Source Page

UI Element	Description
Sources	Add Source: Provides the following options: Add Embedded Performance Component Source: The Embedded Performance (Coda) component collects performance counter and instance data. Add External Source: Uses the data sent from an external program (the opcmon command-line tool, for example) as the source for a threshold alarm. HPE Operations Agent does not poll the external program but waits for values to arrive. Add Management Information Base Source: Uses entries in a Management Information Base as the source for a threshold alarm. Add Program Source: Uses the data sent from an external program as the source for a threshold alarm. HPE Operations Agent runs the external program at each polling interval. Add Real Time Performance Measurement Source: Uses data gathered by the performance monitor as the source for a threshold alarm. Add Windows Management Instrumentation Source: Uses information in the WMI database as the source for the threshold alarm. Policies with multiple sources require you to write scripts to evaluate the threshold levels. Note that switching from single to multiple sources automatically converts the rules to Perl Script. Make sure that the scripting language that you choose will run on the operating system where you intend to use the policies. Copy Source: Copies and inserts the copy below the selected source for editing. Delete Source: Deletes the selected source. Short Name and Description are labels that you choose to help you recognize the value or metric for a threshold source. These labels are visible in the Source Page and are helpful if you write a policy with multiple sources. When using a script to determine the threshold level, these names are used in the script to identify the sources. Store in Coda: You can enter a Data Source, Object and optionally a Metric of your own invention here. The policy will create them in the Embedded Performance Component (Coda) and will store the data from the policy's source at each polling interval. The data is then available for other uses. For example, you can use data stored in the Embedded Performance Component to create graphs with Performance Graphing. Caution For each WMI instance class, you must specify a dedicated CODA object. For example, you can store all WMI instance classes of the type Win32_SystemUsers in a CODA object "users", but you cannot store WMI instance classes of the type Win32_LogicalDisk in the same CODA "users" object. For Win32_LogicalDisk instance classes, use the CODA object "logical_disk", for example.
Embedded Performance Component	The Embedded Performance Component collects performance counter and instance data. You can use these metrics in defining event/action thresholds that generate alarms in real time based on availability, response time, and throughput measurements. Data Source: CODA Object: GLOBAL, CPU, NETIF, FILESYSTEM, DISK Metric: metric to be collected (for example GBL_CPU_TOTAL_UTIL) You can view a list of available metrics in the Performance Agent Dictionary of Operating System Performance Metrics, which is available at HP Software Product Manuals. (Select the product Operations Agent, the required version, OS, and language.) About Metrics The Embedded Performance Component collects the following types of metrics: Basic (golden) metrics. These are approximately 30 metrics that are collected for all supported platforms. They can be used to answer most of your questions about a system's global configuration, CPU, disk, swap, and memory usage and have been chosen to offer the best information for the widest number of platforms. Additional metrics. The data collection component also provides you with additional performance metrics on each of the supported platforms. Although these metrics vary by platform, they are available on most platforms and are generally useful for drill down and diagnosis on a particular system. The collection interval is five minutes. All metrics, including golden metrics and the additional metrics, are collected. The data is kept in the data store for up to five weeks, at which time a week's worth of data is rolled out. Note The embedded performance component must have the Physical Disk Object available to report the disk metrics. To get the disk metrics reported on a node, you must run diskperf -Y to enable the counters under the Physical Disk Object.
External	Select External if you want to use the data sent from an external program as the source for a threshold alarm. The program must produce and deliver values to the policy (see opcmon). If you choose this source, the program will not be started or stopped by the HPE Operations Agent. If you want HPE Operations Agent to run the external program, choose Program instead.
Management Information Base	Select Management Information Base if you want to use entries in a Management Information Base as the source for a threshold alarm. You must specify the MIB ID and the node where the ID is produced. MIB ID: Object ID assigned to the MIB (for example, 1.3.6.1.4.1.11.2.3.9.4.2.1.1). On Node: Fully qualified domain name of the node where the OID is produced. HPE Operations Agent uses the default community `public` for SNMP queries. If the MIB object resides in another community, the community name must be set on the node where the MIB monitoring takes place. (Use ovconfchg to set the parameter `SNMP_COMMUNITY <community>` in the `eaagt` namespace.) Note Instance filters are not available for threshold policies based on the source MIB.
Program	Select Program if you want to use the data sent from an external program as the source for a threshold alarm. The external program will be started by HPE Operations Agent, and must produce and deliver values to the policy. If you do not want HPE Operations Agent to control when the external program runs, choose External instead. Program: Type the complete path and extension of the program that you want to run on the managed node (for example, `%OvDataDir%\bin\instrumentation\collector.exe`). The file that you specify should exist on the node. If you want to automatically deploy the program that runs on the managed node, configure it as instrumentation for this policy You can use policy name variables in Program: `<$FULLNAME>` Returns the name of the policy and the source, concatenated with a hyphen (-). Sample output: `example_policy_name-example_source_name` `<$NAME>` Returns the name of the policy, which you specify when you save the policy. Sample output: `example_policy_name` `<$SRCNAME>` Returns the name of the source, which you specify in Short Name. Sample output: `example_source_name` The agent resolves these variables before it starts the program. This enables you to rename the policy without modifying the program name. If you precede a variable with a backslash (\), the agent ignores the variable. It is possible to disable policy name variables by setting the parameter `OPC_MON_DISABLE_PROG_VARS` to `TRUE` in the `eaagt` namespace on the monitored node.
Real Time Performance Measurement	Select Real Time Performance Management if you want to use data gathered by the performance monitor as the source for a threshold alarm. Object: Object entry in the Performance Manager. Counter: Counter entry in the Performance Manager. Instance: Instance entry in the Performance Manager. For a complete listing and description of all default object counters, see the documentation that Microsoft provides. Additional Configuration If the counter has a percent sign (%), it can be omitted if you want to receive the raw value instead of a percent For instances which have parent instances, a question mark (?) can be used as a wildcard to match any parent instance. For example: `?/C:` matches `0/C` and `1/C` Examples The percentage of free disk space on a C drive on SCSI port 0: Object: LogicalDisk Counter: % Free Space Instance: `0/C:` The number of free megabytes on any C: drive: Object: LogicalDisk Counter: Free Megabytes Instance: `?/C:` The available bytes of RAM: Object: Memory Counter: Available Bytes Instance: empty The amount of CPU time used by a specific process: Object: Process Counter:% Processor Time Instance: `process name` The paging file utilization: Object: Paging File Counter: % Usage Instance: `/DosDevices/C:/pagefile.sys`
Windows Management Instrumentation	Select Windows Management Instrumentation if you want to use information in the WMI database as the source for the threshold alarm. WMI Namespace: The namespace that contains the data that you want to monitor. Instance Class Name: The instance that contains the property that you want to monitor. Property Name: The property that you want to monitor. The property should in most cases be either an integer or a Boolean value. If you choose any other type of property (for example, a string), the policy will automatically restrict the choice of threshold level to VB Script, or Perl Script and you will need to write a script that interprets the string and sets the Rule object to True or False. Non Agent User: If selected, the agent accesses the node's WMI database using the following account information. This account must exist on the agentless node and must have local administrator privileges. If not selected, the agent account is used. Username. User name of the account that the agent will use to connect to the WMI database. Password. Password of the specified user account. Enable policy parameter in Password field. Enables you to enter a variable in the Password field, for example `%%password%%`. A corresponding policy parameter should exist in the Policy Parameters tab.
Polling Interval	How often the policy checks the source for new information. To increase performance, the polling interval should be as large as possible, while still being frequent enough to monitor data at the rate that it is expected to change. A policy begins to evaluate data after the first polling interval passes. A shorter polling interval is better when you are testing a policy. To modify the time, click the button and use the drop-down lists to specify increments of days, hours, minutes, or seconds. To insert a parameter in a time field, type the parameter in the format `%%<VariableName>%%` or drag and drop the parameter from the Policy Parameters tab. When dropping a numeric parameter in a time field, the policy editor appends an `s` to the parameter to indicate that the parameter specifies the time in seconds (for example, `%%interval%%s`). Default value: 5 minutes

Threshold Rules—Overview

UI Element	Description
	Create New Threshold: Adds an empty threshold rule to the list for you to edit.
	Copy Threshold: Copies the selected threshold rule. You can then rewrite the description of the copied rule and edit the rule.
	Delete Item: Deletes the selected threshold rule.
	Move Up. Moves the selected threshold rule higher in the rule order.
	Move Down. Moves the selected threshold rule lower in the rule order.
<Move to>	Entered number is used to select the threshold rule with that sequence number in the list of rules. To select a specific threshold rule in the rule list, type the rule's sequence number in the <Move to> field and click the button.
<Search Thresholds>	Entered search string is used to search the threshold rule descriptions and highlight only the rules containing the specified string. To search for threshold rules with specific text strings in the rule description, type the string in the <Search Thresholds> field and click the button. The first matching rule is selected in the list of rules. Click the and buttons to move the previous and next matching rule.
	Activate/Deactivate Threshold Filter. Activates and deactivates the threshold rule filter.
Seq.	Sequence number of the threshold rules. Rules are evaluated in a specific order. When one condition is matched, no additional rules are evaluated.
Threshold Level Description	Description of the threshold rule. It is good practice to use a description that helps you remember what the rule does.

Threshold Rules—Definition Tab

UI Element

Description

Threshold Level Description This is a name you give to the rule to help you identify it. This name is visible in the rules list.

Threshold Limit (Minimum or Maximum)

Minimum thresholds: <= (less than or equal to): Set the value that triggers an event if the monitored value is equal or lower.

Maximum thresholds: >= (greater than or equal to): Set the value that triggers an event if the monitored value is equal or higher.

Use the following syntax guidelines when specifying the minimum or maximum threshold:

Sequence of Digits:

May include a decimal separator. (The character used as the separator is determined by the operating system language.)
For example: 0.5, 100.1

Sign (optional):

Plus sign (+). For example: +50

Minus sign (-). For example: -730

Exponent (optional):

Exponent character: e or E. For example: 15e2, 7E4

Exponent sign. For example: 8e+2, 4E-2

One or more decimal digits. For example: 25.88e4

Tip If you set a minimum or maximum threshold limit, you can override it for individual nodes.

To override a threshold limit on an individual node, set a parameter locally on the node in the eaagt.thresholds namespace. Specify the parameter value in the following format:

<policy_name>/<threshold_level_description>/<limit>:<reset_value>

For example, if you have a policy called cpu load with a threshold level called condition critical that you want to override with the limit 75 and the reset value 70, set a parameter with the following value:

cpu load/condition critical/75:70

The following limitations apply:

Specify <policy_name> and <threshold_level_description> exactly as they appear in the policy editor. The first and last slash marks (/) delimit the <threshold_level_description>, which can itself contain slash marks.
<reset_value> is required, even if it is the same as <limit>.

Set the parameter using one of the following methods:

Deploy a node info policy that contains the following line:

<parameter_name>(thresholds) <parameter_value>

The <parameter_name> can be any alphanumeric string that is unique within the eaagt.thresholds namespace. Adding (thresholds) after <parameter_name> ensures that the node info policy sets the parameter in the eaagt.thresholds namespace.
Use the command ovconfpar with the following syntax:

ovconfpar -change -host <node_hostname> -ns eaagt.thresholds -set <parameter_name> <parameter_value>

The <parameter_name> can be any alphanumeric string that is unique within the eaagt.thresholds namespace.

Threshold Limit (Perl or VB Script)

Write a script that evaluates the sources you are monitoring and sets the Rule Object to either TRUE or FALSE.

The script should use the short names and the policy objects to access the value for each source, and should perform some calculation to determine if a threshold has been crossed. The script should set the Rule Object to TRUE if the threshold has been crossed or FALSE if it has not been crossed.

Note

HPE Operations Agent uses a generic Microsoft scripting engine to run VBScript scripts. You can therefore use standard VBScript objects (for example, the FileSystemObject object) in your scripts. Objects that are specific to wscript or cscript (for example, the WScript object) are not supported.
The agent runs as a service that has no standard input, standard output, or standard error streams. Therefore, the predefined file handles STDIN, STDOUT, and STDERR are not available for Perl scripts in measurement threshold policies. It is also not possible to open file handles that use command pipes or capture the standard output from commands within backticks (`).

Short-Term Peaks

Since it may not be reasonable to create an event when a threshold is exceeded only for a short time, you can define a minimum time period over which the monitored value must exceed the threshold before generating an event. For an event to be sent, the value must be greater than the threshold each time the value is measured during a duration that you select.

Ignore single short-term peaks occurring within: Select a value that is a multiple of the policy's polling interval. For example, if the polling interval is 2m (two minutes), set the short-term peak duration to 4m, 6m, 8m, or 10m (and so on). If the duration is set to 0 or the box is left empty, an alarm is generated as soon as HPE Operations Agent detects that the threshold has been equaled or crossed.

To modify the time, click the button and use the drop-down lists to specify increments of days, hours, minutes, or seconds.

To insert a parameter in a time field, type the parameter in the format %%<VariableName>%% or drag and drop the parameter from the Policy Parameters tab. When dropping a numeric parameter in a time field, the policy editor appends an s to the parameter to indicate that the parameter specifies the time in seconds (for example, %%interval%%s).

Reset

The reset value is a limit below which the monitored value must drop (or exceed, for minimum thresholds) to return the status of the monitored object to normal. After the status of a monitored object returns to normal, a new start event can be issued if the monitored value again crosses the threshold value. You can either use the same value as the threshold limit, or specify a different reset value.

Reset value is same value as threshold limit
Specify a special reset value for the threshold level
- Minimum thresholds: <source name> < (less than)
- Maximum thresholds: <source name> > (greater than)
- Script thresholds: Write a script that evaluates the sources and determines the reset value.

Threshold Rules—Actions Tab

UI Element	Description
Start Actions	Start actions are carried out the first time that the threshold is met or crossed. Edit the "Start Actions" event: Opens the Start Action tab, which enables you to define what the policy should do after evaluating a particular threshold level.
Continue Actions	Continue actions are carried out at each polling interval if the start action of the rule was carried out at a previous polling interval, and the reset value is not reached. Define special "Continue Actions": Enables continue actions for this rule. Edit the "Continue Actions" event: Opens the Continue Action tab.
End Actions	End actions are carried out after the threshold crosses the reset value, only if the start action for that rule was carried out. If the value drops below two thresholds within one polling interval, the end actions of the lowest rule that performed start actions are carried out. Start the specified "End Actions": Enables end actions for this rule. Edit the "End Actions" event: Opens the End Action tab.

UI Element

Description

Start Actions

Start actions are carried out the first time that the threshold is met or crossed.

Edit the "Start Actions" event: Opens the Start Action tab, which enables you to define what the policy should do after evaluating a particular threshold level.

Continue Actions

Continue actions are carried out at each polling interval if the start action of the rule was carried out at a previous polling interval, and the reset value is not reached.

Define special "Continue Actions": Enables continue actions for this rule.

Edit the "Continue Actions" event: Opens the Continue Action tab.

End Actions

End actions are carried out after the threshold crosses the reset value, only if the start action for that rule was carried out. If the value drops below two thresholds within one polling interval, the end actions of the lowest rule that performed start actions are carried out.

Start the specified "End Actions": Enables end actions for this rule.

Edit the "End Actions" event: Opens the End Action tab.

Threshold Rules—Start Actions Tab

UI Element	Description
Event Attributes	Enables you to set the attributes of the start event.
Event Correlation	Enables you to set correlation options for the start event.
Custom Attributes	Enables you to add custom attributes to the start event.
Instructions	Enables you to add instruction information to help operators handle the continue event.
Advanced	Enables you to set the advanced attributes of the start event.
Actions	Enables you to add automatic and operator-initiated commands to the start event.

Threshold Rules—Continue Actions Tab

UI Element	Description
Event Attributes	Enables you to set the attributes of the continue event.
Event Correlation	Enables you to set correlation options for the continue event.
Custom Attributes	Enables you to add custom attributes to the continue event.
Instructions	Enables you to add instruction information to help operators handle the continue event.
Advanced	Enables you to set the advanced attributes of the continue event.
Actions	Enables you to add automatic and operator-initiated commands to the continue event.

Threshold Rules—End Actions Tab

UI Element	Description
Event Attributes	Enables you to set the attributes of the end event.
Event Correlation	Enables you to set correlation options for the end event.
Custom Attributes	Enables you to add custom attributes to the end event.
Instructions	Enables you to add instruction information to help operators handle the continue event.
Advanced	Enables you to set the advanced attributes of the end event.
Actions	Enables you to add automatic and operator-initiated commands to the end event.

Send Help Center feedback