Troubleshooting Scenarios

Assets or Child Tags Missing in the Search Result

Child tags expected to match the search filter are not available to plot in a chart.

Description

One or both of the following scenarios apply:

  • You plot child tags by searching for child tags within the context of the selected enterprise, site, segment, or asset. You expect to see more tags matching the search filter within the context of all child tags below the selected node (enterprise, site, segment or asset) up to the last leaf. However, the result does not include all tags matching the search criteria. As a result, the tags unlisted cannot be plotted on the chart.
    Note: When selecting an item:
    • If the result is an asset, the context is automatically set to the selected asset, and a new analysis appears.
    • If the result is an enterprise, site, or segment, the context is automatically set to your selection.
  • You add secondary assets to a chart. You expect to see assets within the context of the selected enterprise, site, segment, or asset. However, the results do not include all child assets for the selected root node. You are unable to add required assets to search further for tags to plot in the chart.

Cause

In Essentials, the asset configuration service stores tenant-specific transitive depth information. Unless explicitly changed during tenant setup, these values are set to the default shown in the following code sample:
{
  "transitiveDepthConfig": {
    "enterprises": 1,
    "sites": 1,
    "segments": 1,
    "assets": 1
  }
}
This transitive depth determines how deep to query the hierarchy when searching for a child node. If your tenant asset model has a depth greater than the default, the search query returns results limited to the level matching the default. For example, if your tenant uses an asset hierarchy with two levels of segments and two levels of assets, but its transitive depth configuration is set to the default value of 1, searching for assets or child tags from the top segment node does not include search results beyond the default depth.

Solution

Contact support to change your transitive depth configuration to match the nodes in your hierarchy, allowing the child tag search to traverse to the last leaf node starting from the selected node. Click the following link to enter a support ticket: APM Support Team: https://digitalsupport.ge.com/ .