The Mappings page enables you to map the log file input data properties, which are the structural fields extracted from log files, to custom variables.
In the BSM Connector user interface, click in the toolbar. Then click Event >
Structured Log File.
In the BSM Connector user interface, click in the toolbar. Then click Metrics >
Structured Log File.
Alternatively, double-click an existing policy to edit it.
Click Mappings to open the policy Mappings page.
A custom variable consists of a map name, a field extracted from the log file by using the OM pattern matching language, and one or more source and target value pairs. For example, you can assign the pattern matching field host
to the map name maphost
, and add a source value of critical
. You can then assign the target value serious
to the variable so that BSM Connector inserts the value critical
into the event in all places where the variable is used and the source value is serious
in the log file.
Input data references use the following syntax: <$DATA:<InputReferenceField>>
Field values originate from the structured log file pattern settings defined for the data source.
For example, the custom variable maphost
has the pattern matching field host
assigned.
Assigning a pattern matching field to a map name is optional. If you do not assign a pattern matching field to a variable, you must add the source value directly to the variable when you insert the variable in an event attribute.
The Sample Data tab shows the following information, if sample data is available:
Input Data Properties
If sample data is available, the Input Data Properties section shows all fields that match the structured log file pattern.
The items in the Input Data Properties section are by default sorted alphabetically in ascending order.
Values for 'host'
This section displays the values of a field selected in the Input Data Properties section. If a value appears more than once, click to show or hide duplicate values. To find values that belong to more than one group, select the value and click
. The Sample Data window opens and shows all fields that have the selected value.
When you drag a field from the Input Data Properties list and drop it on the Default Value Mapping List, BSM Connector automatically adds the default prefix map
to the map name and inserts the pattern matching field. You can then drag one or more structured log file source values from the values list and drop them on the Source Value list. You then finally only have to type the target values.
This task describes how to map pattern matching fields to custom variables.
Create one or more custom variables.
If you are working with sample data, drag the field from the Input Data Properties list to the Map Name column. BSM Connector automatically adds the default prefix map
to the map name and inserts the group name.
Alternatively, click above the Map Name column and type the variable name in the map name field. Fields are optional. If you do not assign a field to a variable, you must add the source value directly to the variable when you insert the variable in an event attribute.
Add source and target value pairs to each custom variable.
If sample data is loaded in
above the Source Value column and type the source and target values in the corresponding fields.
Optional. In the Indicators tab, add indicators to the source or target value fields. After loading the indicators from the OMi server, the Indicators tab shows a hierarchy of configuration item types.
To insert an indicator in a source or target value field, drag the indicator state (for example, HTTPServer:Normal
) from the Indicators tab and drop it on the corresponding field.
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 |
---|---|
<Search Properties> ![]() ![]() |
Entered search string is used to find a pattern matching field . The list changes as you type; only matching items appear. To clear the search results, click |
![]() |
Find Matching Events. To find values that belong to more than one pattern matching field , select the value and click ![]() |
![]() |
Toggle Deduplication. Shows or hides duplicate values. |
Input Data Properties |
Shows all pattern matching fields that are extracted from the log file by using the OM pattern-matching language. Note: The Sample Data tab is empty if no sample data has been loaded into the policy or if the sample data does not match the structured log file pattern specified in the source page. See also Configuring Data Source in Structured Log File Policies. |
Values for <...> |
Displays the values of the pattern matching field selected in the Input Data Properties section. |
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. |