The Evaluate Paths displays all the paths defined on the Active Console workspace. It can also identify how expensive these paths are.
To access the Paths dockable, go to Active Console > Tools > Evaluate Paths.
Each field is accessible with a double-click. When you double-click a path, the Active Console opens the path location in a new dockable.
In this example, the
geneos:// ac / Show Critical Alerts on cells path is opened:
The Filter Configuration screen displays:
Note: The listed paths in this dockable do not automatically update.
The Evaluate Paths has three main functions:
- Refresh the view — clears the evaluation results.
- Evaluate — checks and displays the approximate evaluation time of a selected path. Right-click the row to evaluate the path.
- Evaluate all
— checks the approximate evaluation time of all configured paths and identifies the expensive path:
- Evaluate Result column — displays the list of expensive paths in milliseconds (ms).
- Expensive path — highlights the most expensive path in orange.
Note: Beginning Active Console 5.5.x, the Managed Entity display name is used in the user readable path.
By setting a rule, you can determine if the XPath value is expensive or not. The result displays N/A for a path if it is not an XPath or is impossible to evaluate:
A path's score represents how expensive an XPath is, or how long it takes for the Active Console to evaluate the configured paths.
Path scoring factors two things:
- Base score — each path is given a base score. The more elements the path contains (Gateway, Netprobe, Managed Entity), the more expensive it can potentially be.
- Filters — you can add a parameter or attribute to a path level. Filters can improve a path's score since it reduces the number of data items it needs to be evaluated on.
Note: XPaths that match too many data items can have consequences because the cluster may not be able to handle all the data. This can possibly reduce performance and response time of the Active Console and dashboards.
The Gateway configuration setup determines if an XPath can be expensive or not:
- If your setup has less than two Gateways with 200 probes, having an expensive path in terms of evaluation time is high.
- If you have more than 20 Gateways with one running probe, then getting an expensive path is unlikely.