~End Point Attributes Page~

This page enables you to view all End Point attributes defined in the system, and manage their configurable settings. In addition, you can define new attributes that are relevant to your organization, to fine-tune the performance analysis and troubleshooting capabilities of the system.

The End Point Attributes tree, on the left side of the page, lists all defined attributes in alphabetical order. Once an attribute is selected, data relevant to that attribute appears in the two tabs on the right side of the page. Clicking the Add icon (at the upper left corner of the page) allows you to define a new attribute.

Settings

The Settings tab allows you to view and update the configuration settings of the attribute selected in the End Point Attributes tree.

Note:

Only users who are assigned the update_or_create_EPA privilege are able to edit End Point attribute settings.

Setting Description/Notes

Attribute name

The name assigned to the attribute. The name must be unique (for example, the names of pre-defined attributes, such as Location, cannot be reused), and its length must be 255 characters or less.

Data collection method

Specifies the method used to collect data for the attribute. Valid values are CSV Mapping, DB Mapping, LDAP Integration, XML Mapping, Advanced Monitor (WMI), Advanced Monitor (Registry), Advanced Monitor (Event Log), Advanced Monitor (WSH), Built in, and Not Assigned. If no method is assigned, a Not Assigned mark appears next to the attribute on the End Point Attributes tree, and the CSV Mapping method may be assigned to it.

Clicking the View/Edit link opens the Data Collection tab, which displays more information about the data collection method.

Use for Incident probable cause classification

Specifies how the attribute is used for root cause analysis:

  • Server Side: The attribute value from the originating End Point is considered.
  • Client Side: The attribute value from the frontline End Point (desktop) is considered.
  • Both: Attribute values from both the originating and frontline End Points are considered.
  • None: The attribute value is not used for root cause analysis.

Enable for Baseline Splitting

Indicates whether or not the attribute is used in baseline split calculations, when the Baseline Split Order feature is used. (Refer to Baseline Settings for details).

An attribute must be used for the Data Warehouse dimension in order to be enabled for baseline splitting. The attribute must remain enabled for baseline splitting as long as it is used for baseline splitting by a monitor.

Display in End Points tab (Attributes page)

Indicates whether or not the attribute is shown in the Attributes sub-tab of the End Points tab.

Include in Data Warehouse End Point dimension

Indicates whether or not the attribute is used by the system for calculation and analysis of the performance data collected by the Aternity Platform. It is recommended to use the Data Warehouse dimension sparingly, as it expands the database and may cause the system to perform more slowly.

When the Data Warehouse setting is changed, a system restart is necessary for the change to take effect.

Note:

An attribute cannot be removed from Data Warehouse as long as it is used for baseline splitting. Due to some system limitations, some End Point attributes cannot change their data warehouse dimension settings.

Data Collection

The Data Collection tab provides information about the data collection method that is assigned to the attribute selected in the End Point Attributes tree. When using the CSV Mapping method, editing is supported.

When the attribute has any assigned data collection method other than CSV Mapping, the information in the Data Collection tab is read-only. When the data collection method is CSV Mapping, data can be configured by specifying the relevant parameters.

Parameter Description/Notes

Source End Point attribute

The attribute from which data is extracted (key) and mapped to the selected attribute (value). For example, if the attribute selected in the End Point Attributes tree is Location, selecting the Subnet Source EP Attribute maps subnet to location, using Subnet, Location key-value pairs listed in the last uploaded CSV file.

Matching method

Supported methods are:

  • Case Insensitive: Strings must be identical, ignoring case, for a match to be made.
  • Subnet Range: Used for mapping of range of IP addresses (subnets). Relevant only when the source attribute is subnet or active subnet.

Missing value replacement

A (string) value for the system to use when no matching value is found (for example, Not Mapped).

Ignored values

A set of keys that should not be matched. The value returned is the key.

Once parameters are specified, a mapping table must be uploaded from a CSV file:

  • Upload New Mapping: An existing CSV file from the system is selected, and the mapping table currently used is replaced with the specified mapping parameters.

To create a mapping file for upload, note the following:

  • There are two fields. The first is the source attribute value, and the second is the target attribute value to map to.
  • The fields are separated with a comma (comma separated values) and there should be a new line between the different mappings.

The following is an example of subnet to location mapping file:

In addition, it is possible to retrieve currently used mapping, using the following command:

  • Download Current Mapping: The system creates a new CSV file (with a user-selected name and location) by downloading the mapping table that is currently used for the selected attribute. If you choose to include unmapped values, all the keys that the system failed to map are listed at the bottom of the CSV file.