The Metric page enables you to indicate default settings for all metrics generated by the policy.
These defaults affect all new and existing rules. You can override the defaults in individual rules if needed. If a rule contains empty event attributes, the agent will use the defaults for the new event.
In the BSM Connector user interface, click in the toolbar. Then click Metric >
XML File.
Alternatively, double-click an existing policy to edit it.
Click Defaults to open the Default Metric Attributes page.
This task describes how to configure metric attribute defaults for all metrics collected by this policy.
Define the metric attributes common to all metrics collected by this policy, such as metric class and name. All metrics in the Basic tab marked with a * are required. Advanced attributes are optional.
Optional. Use the Sample Data tab to drag XML properties (XML elements and attributes) and values to the attribute boxes. Alternatively, you can type the path to the XML property or value directly into the attribute box.
XML properties use the following syntax: <$DATA:/<XMLProperty>
>
<XMLProperty>
is the path from the root XML element of XML data to a specific XML element or attribute within that data. XML path uses slashes (/) as the path delimiters.
BSM Connector replaces the XML property at runtime with the value of the specified XML element or attribute. If you insert an XML value, the value will be used.
Note: The Sample Data tab is empty if no sample data is loaded into
Optional. Use the Mappings tab to add mapping definitions to the attribute boxes.
Mappings are custom variables that you define in the mappings tab (see also Configuring Metric Defaults in XML File Policies). The default name of the mapping variable is map<XMLProperty>
, for example mapSeverity
.
Alternatively, type the custom variable into the attribute box using the following syntax:
Map Name list contains the map name of the variable: map<XMLProperty>
, for example mapSeverity
.
Input Data Property list item: <$DATA:/<XMLTag>/<XMLProperty>>
For example, the custom variable mapSeverity
has the following input data property: <$DATA:/PerformanceAlert/Severity>
where Severity
is a child element of PerformanceAlert
.
Optional. Use the Operators tab to apply operators to the attribute values. Two functions are available:
<$MATCH()>
, to test a string or a variable against a pattern. The $MATCH function accepts three or four parameters:
- the input string
- the pattern definition
- the output string if pattern matches on the input string
- the output string if the pattern does not match (optional)
Example: The data of the input field hostname start always with "TEST" (for example "TESTABC"). The $MATCH function to use the string after "TEST" is as follows:
$MATCH(<$DATA:hostname>,TEST<*.prefix>,<prefix>)
<$DATETIME(FORMAT,VALUE)>
, to convert the format of dates from the common format to the UNIX systems time (Epoch time) format.
For detailed description of the format, see Pattern Matching in Policy Rules.
Note: To apply operators to the attribute values, you can drag and drop them to a text field in the left pane of the same policy editor page. The appropriate tooltips are shown while performing this operation, which describe the role of the dragged operator.
Optional. Use the Indicators tab to add indicators to the source or target value fields. After loading the indicators from the connected OMi server, the Indicators tab shows a hierarchy of configuration item types.
Optional. In the Policy Variables tab, add policy variables to
HP recommends to surround variables with quotation marks, for example "<$MSG_NODE>"
or "<$MSG_GEN_NODE>"
, at least for those variables whose values can contain space characters.
UI Element | Description |
---|---|
Data domain |
The namespace of the integrated performance records, used in the Operations Agent store to avoid clashes. Example: "BSMConnector" |
Metric class |
Defines the metric class. Metric class and metric name are concatenated as the metric name that appears in the Operations Agent store and consumers. Example: "Windows CPU Monitor" |
Metric name |
Defines the metric name. Metric class and metric name are concatenated as the metric name that appears in the Operations Agent store and consumers. Example: "CPU Utilization" |
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 ![]() 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 more information about CI resolution in OMi, see the OMi User guide or online help. |
Node |
Used to identify a node-like CI to which the performance records are associated to. Example: "dbsys1.company.com" |
Value |
The actual performance value. It is automatically converted to a double-precision number. Example: 80 |
Time measured |
The time stamp when the value was determined in the third-party system, expressed in the following formats:
|
Description |
|
---|---|
<$MATCH(inputStr,patternDef,outputStr,outputStrNoMatch)> |
Tests a string or variable against a pattern. The $MATCH function accepts three or four parameters: - the input string - the pattern definition - the output string if pattern matches on the input string - the output string if the pattern does not match (optional) Example: The data of the input field hostname start always with "TEST" (for example "TESTABC"). The $MATCH function to use the string after "TEST" is:
|
<$DATETIME(FORMAT,VALUE)>
|
Converts regular dates to UNIX time (Epoch time). |
Description |
|
---|---|
![]() |
Refresh. Loads the configured indicators from the Note:
|
<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 |
<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. |