Showing results for 
Search instead for 
Did you mean: 

Analytics: Using the Component Filter to Refine Queries

This article is part of a series, beginning with Analytics Application - Concepts and Metrics Explained


The Analytics Application included in Services Director can apply a Component Filter to refine queries. The values shown in the Component Filter are also calculated by a query.


The intention of the Component Filter is to show the user all the permutations of Locations, Clusters, vTMs, vServers, Pools, and Nodes that appear in the selected part of the dataset. The values are derived as follows:


  • Filter away all records outside the time range.

  • Apply any further filters (from the Extended Filter).

  • Count records, splitting by Location, Cluster, vTM, vServer, Pool and Node.
    NOTE - The count is unnecessary, but is the simplest way to achieve the split.

  • Ignore the counts, while retaining the combinations of Location, Cluster, vTM, vServer, Pool and Node revealed by the split.


The result of this is an internal table with columns for Locations, Clusters, vTMs, vServers, Pools and Nodes. Each row of this table represents a unique end-to-end 'path' that one (or more) connections/requests have taken through the estate, with time period and any filters applied.

Any given category value will likely appear more than once, in combination with different values from other columns.

Finally, the drop down boxes (LocationsClustersvTMsvServersPools, and Nodes) for each category are filled with all the unique values from the corresponding column in the internal table.

The query is re-run whenever the user navigates in a way that invalidates the table of results, such as they change the time range, or apply an Extended Filter clause.

Note that some local optimisation allows values to be selected in the component filter without re-running the query.

This article is part of a series, beginning with Analytics Application - Concepts and Metrics Explained

Prev: Reporting on Top Events

Next: Using Sampling to Reduce Query Times


Version history
Revision #:
3 of 3
Last update:
‎06-15-2018 03:06:AM
Updated by: