Identify Areas of Concern Using Filters

Filters let you narrow down your search for components by attribute name and value. Filters remove information from the dataset that dashboard and map displays. Use Filters to identify areas of concern while monitoring your environment. Filter out groups of unaffected components to simplify the dashboard and map for monitoring and triage. Filters are cumulative working from left to right. You can filter the results of one filter with another. You can build up layers of filters to drill into specific areas of an environment. Filters are persistent between the dashboard and map.
apmdevops106
HID_Filters
Filters let you narrow down your search for components by attribute name and value. Filters remove information from the dataset that dashboard and map displays. Use Filters to identify areas of concern while monitoring your environment. Filter out groups of unaffected components to simplify the dashboard and map for monitoring and triage. Filters are cumulative working from left to right. You can filter the results of one filter with another. You can build up layers of filters to drill into specific areas of an environment. Filters are persistent between the dashboard and map.
3
2
Application Performance Management has the following filter features:
  • Filter by following a transaction path
  • Filter components by any attribute
  • Apply multiple filter groups 
  • Include experience node in the filter result
  • Drag-and-drop individual filters across the filter groups
Filter Groups and Attribute Filters
A
filter group
defines the set of attribute names and values that are displayed on the map and dashboard. All other components are removed from the data set. Within a single filter group, each additional filter condition narrows the
resulting set of nodes displayed.
An
attribute filter
removes all components from the dataset that do not have attribute names and values in the filter condition. A
transaction path filter
removes all components from the dataset that do not have transaction path values in the filter condition.
  • Filters within a single filter group are combined with an AND operator. Each filter condition can be an attribute filter or a transaction path filter. Add a filter group to include a second set of filtered data to the map and dashboard.
  • Different filter groups are combined with an OR operator. The map displays all nodes that meet the criteria of filter group 1 and all the nodes that meet the criteria of filter group 2.
You can drag-and-drop filter conditions to edit filter groups. If you drag-and-drop  a Transaction Path Filter between filter groups, the filter becomes an attribute filter. You cannot move transaction path filters between filter groups. You cannot change an attribute filter into a transaction path filter. Delete the attribute filter and create one as a transaction path filter.
You can change the order of the filters by using drag-and-drop. You can change the order of filters, move them across filter groups and into or out of transaction path filters. The only limitation is that you cannot move the transaction path filter as a whole. If you move the last filter condition out of the transaction path filter frame, the frame disappears.
Set a Transaction Path Filter
Application Performance Management generates map data by sampling transaction traces. A record exists of every transaction path that passes through any component.
Identifying all transactions in large environments can lead to generating high numbers of vertices, which can affect performance. To prevent data explosions in large environments, this feature can be disabled.
A transaction path filter identifies all components in all transaction paths with attribute values that are specified in the filter criteria. For example, you want to see on the map all transactions that go through any component that has the Location attribute Paris. If you set a transaction filter for the location Paris, the map displays all the components for the transactions that pass through the Paris nodes.
: Transaction paths are taken from the experience node, which is the first monitored front-end component and the beginning of the transaction path. An experience node contains an extra attribute called Experience. If a transaction forks at any stage, the transaction path filters identify all components of that transaction. The transaction path filters also identify forked branches regardless of where the specified attribute lies within the transaction.
Follow these steps:
  1. Click
    Add filter
    , add filter criteria, and select
    FOLLOW TRANSACTION PATH
    .
  2. (Optional) Select the
    Include experience node
    checkbox.The experience node is the first monitored front-end component and the beginning of the transaction path. Experience attribute in filters contains the experience node including all other nodes in the transaction path. If you select
    Include experience node
    , you add all experience nodes that use the filtered nodes.
You can manually remove particular nodes. Assign a custom attribute to the node and then filter that attribute out.
You set a transaction path filter.
Create a Filter Group
Follow these steps:
  1. Click the plus icon next to a filter.
    A drop-down list of attribute names appears.
  2. (Optional) Select
    FOLLOW TRANSACTION PATH
    .
  3. Select
    Add new filter group
    .
  4. Select an attribute name to filter by.
  5. Click the filter condition drop-down list and clear the attribute values to be removed by the filter.
    Status icons next to the filter values indicate the health status of the associated components in live mode only.
  6. (Optional) Add further filter criteria. Click the plus icon inside the blue frame and add more attribute names to the Transaction Path Filter condition.
A Transaction Path Filter condition can include one or more attribute names.
You created a filter group.